corelinux-develop

[Corelinux-develop] Thread State Transition Diagram (continued)

[Hans D. <dul...@co...>]

I hit the "Sent" button accidentally but my e-mail was not complete.
So here is the more complete one.

1) ThreadContext.hpp declares an enum type ThreadState
(THREAD_WAITING_TO_START,
THREAD_STARTING, ...., THREAD_START_FAILED).

2) The Thread::get.*Count() routines depend on Thread::theThreadState to
report
the correct number of threads in specific state.

How is the thread state transition diagram looks like? Here is what I
infered from the existing code:

When a new thread is created its state is WAITING_TO_START,
When the thread is started from startThread its state is set to RUNNING
(this is what added to version 1.17 and checked in as version 1.18).
May be I should change this to STARTING, instead of RUNNING.

But then how the transition from STARTING to RUNNING will take place?


-- 
Hans Dulimarta, Ph.D. |             dul...@co...
Research Associate    |  http://www.egr.msu.edu/~dulimart   
P: 517-432-7589       | http://snapsource.sourceforge.net
F: 760-281-7691       |  http://corelinux.sourceforge.net
ECE Dept. Michigan State University, E. Lansing, MI 48824

Re: [Corelinux-develop] Thread State Transition Diagram (continued)

[Frank V. C. <fr...@co...>]

Hans,

If the user doesn't register specific handlers, the 
ThreadContext::cloneFrameFunction does the state changes.

Hope this helps.

Frank V. Castellucci

Hans Dulimarta wrote:

> 
> I hit the "Sent" button accidentally but my e-mail was not complete.
> So here is the more complete one.
> 
> 1) ThreadContext.hpp declares an enum type ThreadState
> (THREAD_WAITING_TO_START,
> THREAD_STARTING, ...., THREAD_START_FAILED).
> 
> 2) The Thread::get.*Count() routines depend on Thread::theThreadState to
> report
> the correct number of threads in specific state.
> 
> How is the thread state transition diagram looks like? Here is what I
> infered from the existing code:
> 
> When a new thread is created its state is WAITING_TO_START,
> When the thread is started from startThread its state is set to RUNNING
> (this is what added to version 1.17 and checked in as version 1.18).
> May be I should change this to STARTING, instead of RUNNING.
> 
> But then how the transition from STARTING to RUNNING will take place?
> 
>