[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [PATCH 0/4] HVM Virtual S3

  • To: "Keir Fraser" <keir@xxxxxxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Fri, 18 May 2007 10:07:27 +0800
  • Delivery-date: Thu, 17 May 2007 19:05:54 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AceX2gAl4h+XcEYPRxOJnM8JUiP1/QAL7oULAAhTZWAACu1RuQAESK7gAAcVONkAADNs4AAAv50gABld9UA=
  • Thread-topic: [Xen-devel] [PATCH 0/4] HVM Virtual S3

>From: Keir Fraser
>Sent: 2007年5月17日 21:34
>On 17/5/07 14:16, "Yu, Ke" <ke.yu@xxxxxxxxx> wrote:
>>> They were posted by your Intel colleague Kevin Tian just a few days
>>> ago.
>> Yes, I see the patches. But as far as I can see, these patches does not
>> save/restore all domains. It only reuse some driver domain
>> logic to suspend/resume the physical devices that driver domain owns.
>Ah, okay, it looks like I misunderstood.
> -- Keir

Great that people are looking at host S3 side. :-)

The host S3 patch only tackles dom0/xen, and leave user level to notify 
all para-domUs and HVM domains before requesting real S3 switch. So 
basically to make a complete eco-system:
        - Need to trigger virtual S3 to HVM domain
        - Need light weight suspend/resume to para-domU (without 
domain destroy) for fast resume. Actually I sent out months ago and 
you suggested to re-send after basic host S3 is ready

Currently host S3 only imposes a last level means to force all domains 
paused in case they're not doing well.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.