| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH 0 of 3] Remus: control tool
On 12/02/09 10:20, Brendan Cully wrote:
> What signal do you have in mind for telling the control stack that the
> guest has completed its resume procedure and is running normally
> again?
>
Hm, point. I was thinking of waiting for the "I'm suspended" hypercall,
but that doesn't help.
It has always worried me that the suspend protocol is very brittle. For
example, there's no way for a guest to reject a suspend attempt, either
because it doesn't support suspending, or it isn't convenient right now,
or it tried but failed. A backchannel xenstore entry would allow the
guest to indicate what stage its up to to the control stack, including
holding off suspend attempts until it is ready to accept new ones. But
that doesn't help much if you want to eliminate the xenstore overhead
from the process...
J
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home