[Xen-ia64-devel] RE: [Xen-devel] RE: [Patch] Fix IDLE issue with sedf scheduler on IA64

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

(ia64 only since this is an archdep solution)

> >Is there a better way (for ia64)?  I kind of like the solution
> >Keir and Ian imply... is it possible in context_switch to simply
> >"refuse" to switch to the idle domain?   E.g. if the idle domain
> >is the target of the switch, instead switch to domain0 (and
> >make it runnable)?
> >
> 
> This seems not easy to be simply done in context_switch without common
> change. Preventing switch to IDLE is easy, and a simple check in
> context_switch can achieve. However the really bad thing is about
> housekeep info within scheduler. Eg. domain0 may have been placed on
> waitq, with begin of next period still far away. Stealing 
> slice of IDLE
> to Dom0 without notifying scheduler, may mess the future 
> decision since
> next schedule will happen on Dom0's context and base on 
> dom0's statistic
> info...

I think domain0 only goes in the waitq at one point -- when
it calls pal_halt_light to idle its virtual machine.  This
case could be easily changed (there is already some code there)
to ensure domain0 is always runnable.

Dan

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel