From: Jeremy Fitzhardinge <jeremy@goop.org>
To: keir.fraser@eu.citrix.com, andy@cs.ubc.ca,
xen-devel@lists.xensource.com, konrad.wilk@oracle.com
Subject: Re: [PATCH 0 of 3] Remus: control tool
Date: Wed, 02 Dec 2009 10:30:14 -0800 [thread overview]
Message-ID: <4B16B236.8000306@goop.org> (raw)
In-Reply-To: <20091202182025.GA4866@zanzibar.quuxuum.com>
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
next prev parent reply other threads:[~2009-12-02 18:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 1:10 [PATCH 0 of 3] Remus: control tool Brendan Cully
2009-11-13 1:10 ` [PATCH 1 of 3] Remus: add python control extensions Brendan Cully
2009-11-13 1:10 ` [PATCH 2 of 3] Remus: add control script to activate remus on a VM Brendan Cully
2009-11-13 1:10 ` [PATCH 3 of 3] Remus: support for network buffering Brendan Cully
2009-11-13 14:18 ` [PATCH 0 of 3] Remus: control tool Konrad Rzeszutek Wilk
2009-11-13 21:36 ` Brendan Cully
2009-12-01 15:20 ` Pasi Kärkkäinen
2009-12-01 16:16 ` Brendan Cully
2009-12-01 23:04 ` Jeremy Fitzhardinge
2009-12-01 23:53 ` Brendan Cully
2009-12-02 8:07 ` Keir Fraser
2009-12-02 18:17 ` Jeremy Fitzhardinge
2009-12-02 18:20 ` Brendan Cully
2009-12-02 18:30 ` Jeremy Fitzhardinge [this message]
2009-12-02 18:25 ` Keir Fraser
2009-12-02 18:34 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B16B236.8000306@goop.org \
--to=jeremy@goop.org \
--cc=andy@cs.ubc.ca \
--cc=keir.fraser@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.