This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Blocking upcall to dom0

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

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.
Xen-devel mailing list