[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] Fix one dead loop case in host S3


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Fri, 07 Sep 2007 11:21:52 +0100
  • Delivery-date: Fri, 07 Sep 2007 03:22:26 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcfwVFyyj8rkFuzwQZagZ9TTehQvnQA5IuLD
  • Thread-topic: [Xen-devel] [PATCH] Fix one dead loop case in host S3

Applied. It looks like Xen's XENPF_enter_acpi_sleep command only gets
invoked after the second write to the pm1a/pm1b control ports. So do we
actually need first-write handling in that hypercall? Is it going to be used
in future?

 -- Keir

On 6/9/07 08:05, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> Wake sts is only required to be checked for S1, and implementation
> is free to not touch wake sts bit for S3. The latter case is observed
> falling into loop on checking wake sts after sleep hypercall returns.
> Actually we only need to check hypercall return value here, and those
> checks belong to Xen instead.
> 
> (For linux-xen staging)
> Signed-off-by Kevin Tian <kevin.tian@xxxxxxxxx>
> 
> Thanks,
> Kevin
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.