All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joanna Rutkowska <joanna@invisiblethingslab.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Jan Beulich <JBeulich@novell.com>,
	Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>,
	Rafal Wojtczuk <rafal@invisiblethingslab.com>
Subject: Re: S3 sleep in dom0 breaks dom0<->domU wallclock synchronization
Date: Tue, 06 Jul 2010 16:09:01 +0200	[thread overview]
Message-ID: <4C3338FD.90201@invisiblethingslab.com> (raw)
In-Reply-To: <C858E525.197BC%keir.fraser@eu.citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1022 bytes --]

On 07/06/10 14:50, Keir Fraser wrote:
> On 06/07/2010 11:27, "Joanna Rutkowska" <joanna@invisiblethingslab.com>
> wrote:
> 
>>> Wouldn't it be much simpler to not introduce any new logic at all and
>>> just let Dom0 tools/scripts take care of properly suspending
>>> (checkpointing) all (minimally all pv, but I would really think treating
>>> different kinds of guests differently here is unnecessary) guests
>>> before doing a host suspend, as Jeremy had suggested in an earlier
>>> reply?
>>>
>>
>> But wouldn't this require dumping all the VMs memory do disk? Can we use
>> xm pause instead, i.e. will it notify VMs properly?
> 
> It just requires the guests to be put through a guest-side suspend/resume
> cycle. The usual tools-side work of saving to disk etc could be elided. Yes,
> it probably makes sense to extend that existing mechanism to include S3 as
> well. Just needs someone to do the work. :-)
> 

Perhaps it will also solve the resume problem on Core i5/HT systems...

joanna.


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 226 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-07-06 14:09 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
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 [this message]
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=4C3338FD.90201@invisiblethingslab.com \
    --to=joanna@invisiblethingslab.com \
    --cc=JBeulich@novell.com \
    --cc=Jeremy.Fitzhardinge@citrix.com \
    --cc=jeremy@goop.org \
    --cc=keir.fraser@eu.citrix.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 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.