Re: [Xen-devel] Blocking upcall to dom0

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

On 1 Mar 2005, at 20:53, Andrew Biggadike wrote:

> > Xen doesn't support arbitrary blocking within itself since it only
> > maintains per-CPU stacks, not per-domain stacks.
> Interesting.  So this means the scheduler is only ever invoked on
> entry to and exit from Xen when there is no Xen state to worry about
> saving?
Or at other times when we really know what we are doing (e.g., 
interrupting long-lived hypercalls).
> > So you have to create a closure manually.
> This is a bit more work than I had bargained for, but it seems doable.
> Does temporarily setting a different schedule_tail() function to
> restore the state from the closure seem reasonable?
I think that would be an excellent place to hook in.

 -- Keir



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel