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

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


  • To: "Ke, Liping" <liping.ke@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Wed, 21 May 2008 08:32:55 +0100
  • Delivery-date: Wed, 21 May 2008 00:33:07 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aci6Rwan30LCwMVNRjCgsXSrb2rzYwAOb9TQAAFWQHAAAIxGwAAAHx6dAACz6YAAAGA27AAfNwegAAK6SY0=
  • Thread-topic: [Xen-devel] [PATCH 0/4] HVM Virtual S3 --- Revised and resent

On 21/5/08 07:31, "Ke, Liping" <liping.ke@xxxxxxxxx> wrote:

> 1. after cpu_reset, seems we need to call vcpu_initialise to reconstruct vmcs,
> otherwise, the domain could not be resumed back and xen has low response then.

I don't like that. We should work out what bit of architectural state needs
to be reset and do that from hvm_vcpu_reset_state().

> 2. yes, we may need to find a way to clear that io_port_write, otherwise, save
> will hang. I add back the clear (defer_shutdown =0) to have a test, then it
> works just fine.

I now agree this is the correct approach, but perhaps we should
vcpu_end_shutdown_deferral() in vcpu_reset().

> 3. in python, seems it will report
>     a. global name "TRIGGER_S3RESUME" is not defined
>     b. global name "HVM_PARAM_ACPI_S_STATE" is not defined

Silly mistakes.

I can help with these a bit. Perhaps I can get myself a test setup today.

 -- Keir



_______________________________________________
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®.