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] hvmloader: add "wakeup from S4 on RTC alarm"bit

To: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] hvmloader: add "wakeup from S4 on RTC alarm"bit to ACPI FADT
From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
Date: Fri, 04 Feb 2011 17:22:28 +0100
Cc: Paul Durrant <Paul.Durrant@xxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 04 Feb 2011 08:23:11 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110204161758.GA482@xxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <c923816861a96328aaf3.1296827392@xxxxxxxxxxxxxxxxxxxxxxx> <C971D41B.169C0%keir@xxxxxxx> <291EDFCB1E9E224A99088639C47620228CFFAD7B5C@xxxxxxxxxxxxxxxxxxxxxxxxx> <4D4C21DC.8080903@xxxxxxxxxx> <291EDFCB1E9E224A99088639C47620228CFFAD7B6A@xxxxxxxxxxxxxxxxxxxxxxxxx> <20110204161758.GA482@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.7
On 02/04/2011 05:17 PM, Tim Deegan wrote:
XenServer has code in the qemu acpi path to actually perform timed wake
from S4 by pulling the RTC state out of the hypervisor.  I thought this
had gone upstream to qemu-xen already; now that we're transitioning to
upstream qemu I'm not sure where it should go.  It will certainly need
tidying for upstream qemu as it's very xen-specific.

There's nothing like that indeed in qemu-xen-unstable.git.

Paolo

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