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/
Home Products Support Community News


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

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Yu, Ke" <ke.yu@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/4] HVM Virtual S3
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 18 May 2007 07:43:54 +0100
Delivery-date: Thu, 17 May 2007 23:40:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <D470B4E54465E3469E2ABBC5AFAC390F013B1E18@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: AceX2gAl4h+XcEYPRxOJnM8JUiP1/QAK20w3AAE2ZE8AOoy7cAAI20ND
Thread-topic: [Xen-devel] [PATCH 0/4] HVM Virtual S3
User-agent: Microsoft-Entourage/
On 18/5/07 03:38, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> I doubt whether this will bring some tricky issues if Qemu happens
> to inject some event after Xen's reset but before Qemu's reset. If
> that event results a stale pending interrupt after Xen resets vPIC or
> vIOAPIC, will that result a spurious interrupt after HVM is resumed?
> By current style, Qemu first reset all virtual devices and thus stop
> interrupt sources. Then it's safe to let Xen do a full reset subsequently.
> Also normally the reason to put Qemu logic into Xen is for performance. For
> virtual S3 interception, it doesn't matter since only resume time is
> the concern.
> Just doubt whether it's worthy of such split anyway. :-)

Okay, let's rename this s3_suspend hypercall to system_reset instead, and
leave it that.

 -- Keir

Xen-devel mailing list