vmark hangs with libthr and libkse

[David Xu]

Jeff Roberson wrote:

>>>>        
>>>>
>>>Why do you need to do adjustrunqueue() in sched_prio?  I also don't
>>>understand the case in sched_switchout().  Can you please explain that?
>>>
>>>
>>>      
>>>
>>adjustrunqueue maintains kg_last_assigned and related things, when a
>>thread's priority is changed,
>>the thread might no longer can be in scheduler's run queue,  instead it
>>will be in ksegrp's runqueue,
>>because there is higher priority thread, and a KSE it attached should be
>>detached now, and the KSE
>>will attach to another higher priority thread, ULE ignores this
>>requirement, as I can understand,
>>ULE is only aware of  1:1 between KSE and thread.
>>It would be nice if scheduler interface is thread aware but not kse aware.
>>    
>>
>
>Yes, wouldn't it be nice..  I don't think it should be ksegrp aware
>either.  oh well, it wasn't my design.
>  
>
SA process doesn't rely on kse and ksegrp because I introduced a 
kse_upcall structure,
so I don't care someone drops kse or ksegrp and makes them as scheduler 
specific data structure.

>Will you commit this patch?
>  
>
Will do.