WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: "Ke, Liping" <liping.ke@xxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 08 May 2008 16:03:15 +0100
Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>
Delivery-date: Thu, 08 May 2008 08:03:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <391BF3CDD2DC0848B40ACB72FA97AD590352E41A@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Aciwyj3GC5kFZyVcS9eJk6QW6cxy6gAO58GAAASSNxAAAR+baw==
Thread-topic: [Xen-devel] [PATCH 0/4] HVM Virtual S3
User-agent: Microsoft-Entourage/11.4.0.080122
On 8/5/08 15:57, "Ke, Liping" <liping.ke@xxxxxxxxx> wrote:

>> Further, do we actually need the s3 resume hypercall? Couldn't we just
>> put the VCPUs and xen-emulated devices into the right state for resume
>> at the end of s3 sleep and just leave the domain paused (i.e.
>> unscheduled)?
> As I can understand, when S3, HVM will perform like native-machine S3,
> all execution context are in memory When resume back, jump to the CS/EIP,
> those vcpus resume execution normally.
> Ke& Kevin, any coments here?

I think part of what Ian means is that you may as well have a single
interface into each device model in Xen -- e.g., hpet_reset(), pit_reset(),
and so on. Rather than have separate poweroff/poweron functions. Apart from
the greater simplicity, some models already have a reset interface, and I'm
not sure the implemented poweroff/poweron splits are all correct.

And then, once the poweron calls are all gone, what else does s3_resume
actually have to do?

 -- Keir




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