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: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, "Ke, Liping" <liping.ke@xxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 15 May 2008 12:51:35 +0100
Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Delivery-date: Thu, 15 May 2008 04:52:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <DD74FBB8EE28D441903D56487861CD9D2E6B9C14@xxxxxxxxxxxxxxxxxxxxxx>
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: Aciwyj3GC5kFZyVcS9eJk6QW6cxy6gAO58GAAASSNxAAAQ9pEAAnjI9gAAQtZQAA9rPlAAAFlo6tABrTxrAADZF8SQAIt2zQAABHtIg=
Thread-topic: [Xen-devel] [PATCH 0/4] HVM Virtual S3
User-agent: Microsoft-Entourage/11.4.0.080122
On 15/5/08 12:45, "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx> wrote:

>> The 'pause' state visible to tools is a specific type of
>> domain_pause(), and
>> *has* to be entered via the pause domctl hypercall. So don't worry --
>> your new type of pause should stack on top of 'xm pause/unpause' no
> problem.
> 
> In fact, does the S3 suspended guest need to go into a pause state at
> all? Presumably we could just let it block?
> Xend does need to be able to know when the S3 suspend has actually
> happened -- there should probably be a VIRQ for this.

S3 suspend is enacted by an I/O port write from the guest, trapped by qemu,
so the final reset of machine state is synchronously triggered by the tools
anyway.

As for pause-vs-block I think this is just a matter of terminology. At the
end of the day we want the domain to not run until s3-resume is triggered.
The natural way to do this within the hypervisor is to maintain a per-domain
is_s3_suspended flag and domain_[un]pause() when this flag toggles.

 -- Keir




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