From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
Joanna Rutkowska <joanna@invisiblethingslab.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>,
Rafal Wojtczuk <rafal@invisiblethingslab.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: S3 sleep in dom0 breaks dom0<->domU wallclock synchronization
Date: Tue, 6 Jul 2010 04:52:45 +0100 [thread overview]
Message-ID: <C858671D.19765%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C3261C8.4000808@goop.org>
On 05/07/2010 23:50, "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:
>> BTW: wouldn't it be good to actually notify them? Consider e.g. DomU
>> that has some device assigned to it (say a NIC) -- if we emulated S3
>> suspend/resume for this DomU, there is a hope it would properly
>> suspend/reinitialize the NIC, wouldn't it?
>>
>
> I guess? That implies some kind of PV S3 suspend and resume event to
> feed into the dom U's device model. What does 2.6.18-xen do?
I don't think our S3 support is very compatible with PV device passthrough.
We support HVM virtual S3, and can S3-sleep HVM guests across real host S3,
but we don't have similar for PV guests.
-- Keir
next prev parent reply other threads:[~2010-07-06 3:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 3:04 S3 sleep in dom0 breaks dom0<->domU wallclock synchronization Rafal Wojtczuk
2010-07-01 14:50 ` Keir Fraser
2010-07-01 14:51 ` Keir Fraser
2010-07-01 15:18 ` Joanna Rutkowska
2010-07-01 16:12 ` Keir Fraser
2010-07-05 19:18 ` Jeremy Fitzhardinge
2010-07-05 19:26 ` Keir Fraser
2010-07-05 22:43 ` Joanna Rutkowska
2010-07-05 22:50 ` Jeremy Fitzhardinge
2010-07-05 23:03 ` Joanna Rutkowska
2010-07-05 23:19 ` Jeremy Fitzhardinge
2010-07-06 9:12 ` Joanna Rutkowska
2010-07-06 16:17 ` Jeremy Fitzhardinge
2010-07-06 3:52 ` Keir Fraser [this message]
2010-07-06 9:10 ` Joanna Rutkowska
2010-07-06 10:02 ` Jan Beulich
2010-07-06 10:27 ` Joanna Rutkowska
2010-07-06 12:50 ` Keir Fraser
2010-07-06 14:09 ` Joanna Rutkowska
2010-07-08 14:06 ` Joanna Rutkowska
2010-07-06 14:53 ` Dan Magenheimer
2010-07-06 16:24 ` 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=C858671D.19765%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Jeremy.Fitzhardinge@citrix.com \
--cc=jeremy@goop.org \
--cc=joanna@invisiblethingslab.com \
--cc=konrad.wilk@oracle.com \
--cc=rafal@invisiblethingslab.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).