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 13:58:07 +0100
Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Delivery-date: Thu, 15 May 2008 05:58:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <DD74FBB8EE28D441903D56487861CD9D2E791455@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: Aciwyj3GC5kFZyVcS9eJk6QW6cxy6gAO58GAAASSNxAAAQ9pEAAnjI9gAAQtZQAA9rPlAAAFlo6tABrTxrAADZF8SQAIt2zQAABHtIgAAZHZYAAAwQEJ
Thread-topic: [Xen-devel] [PATCH 0/4] HVM Virtual S3
User-agent: Microsoft-Entourage/11.4.0.080122
On 15/5/08 13:42, "Ian Pratt" <Ian.Pratt@xxxxxxxxxxxxx> wrote:

>> 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.
> 
> We wouldn't need to do the pause if the code after the magic port write
> did "cli;hlt". Does it do this or loop?
> [On real hardware the effect of the port write wouldn't be immediate, so
> it must do something]

It spins. But to take advantage of that we have to restructure
s3-suspend/resume so that the reset of machine state happens in the resume
hypercall. At that point suspend, from the point of view of Xen, becomes a
no-op. I suppose we could do that... It seems a bit odd though and I don;t
know that it's guaranteed that all operating systems will happily spin
forever waiting for S3 oblivion. Some may time out.

 -- Keir



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