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

["Ke, Liping" <liping.ke@xxxxxxxxx>]

Ke, Liping wrote:
> Hi, Keir
> Thanks for the refactory for xen interface! It's fine.
> And I think deleting \_PTS and \_WAK will not affect virtual S3 when
> "mem" is available in /sys/power/state.
> For 3) So currently save/restore could not perform on a s3_suspended
> Machine since the domain is not running?I will have some try tomorrow.
Not Machine I mean domain here. Sorry for typo.
> Thanks a lot!
> Criping
> 
> 
> 
> Keir Fraser wrote:
>> Mostly checked in, but:
>> 
>>  (1) I made some big changes to the Xen interface and implementation
>>  (2) I removed some extra ACPI objects you added to the DSDT which
>> seemed to serve no purpose. Perhaps they were old debugging aids?
>>  (3) I did not take most of the xend changes. I'm not sure exposing
>> this through dominfo and into the VM power state mechanisms is the
>> right thing to do. At least we should have a reason to do it. Also
>> the code in XendCheckpoint.py around save/restore and S3 looked a bit
>> dodgy to me. I might consider it in a separate clearly explained
>> patch. 
>> 
>>  -- Keir
>> 
>> On 20/5/08 07:59, "Ke, Liping" <liping.ke@xxxxxxxxx> wrote:
>> 
>>> Hi, all
>>> According to feedback those days, we revised and resend HVM virtual
>>> S3 patch. Changes includes: 1) We merged part of original S3
>>> suspend and resume path, paused domain 
>>> 
>>>     when do s3 suspend. Then unpause domain when s3 resume.
>>> 2) Add xm trigger <domid> s3suspend interface for triggering
>>>     s3_resume operation for the suspended domain.
>>> 3) Add a flag for mark s3_suspended domain
>>> 4) make s3 suspended domain could be saved/restored.
>>> 
>>> We tested the following four patches based on cs17655 on below
>>> environment: 
>>> 
>>> HVM guest FC8-32e X-window mode, vtd-enabled
>>> HVM guest FC8-32e X-window mode, no-vtd with PV drivers vif
>>> HVM guest FC6-32p test mode, vtd-enabled
>>> HVM guest FC6-32p test, no-vtd with PV drivers vif
>>> Also we test s3_suspend->save->restore->s3_resume operation seq for
>>> above four scenario. All works.
>>> No-windows HVM is tested since we have now vga drivers in qemu
>>> don't support. 
>>> 
>>> Thanks& Regards,
>>> Criping
>>> 
>>> 
>>> 
>>> [PATCH 0/4] HVM Virtual S3
>>> 
>>> These set of patches are our prototype for HVM virtual
>>> ACPI S3 support:
>>>  - patch 1/4: Xen interface for HVM S3
>>>  - patch 2/4: QEMU interface for HVM S3
>>>  - patch 3/4: rombios interface for HVM S3
>>>  - patch 4/4: xend interface for HVM S3
>>> 
>>> The main idea is:
>>> - emulate ACPI PM1A control resiger in QEMU to capture guest S3
>>> request 
>>> - when QEMU capture guest S3 request, it call hypercall to trap to
>>> Xen 
>>> - HVM suspend operation now includes below steps:
>>>   1. reset all vcpus, timers
>>>   2. resume HVM by setting HVM vcpu EIP to 0xfff0, cs base to
>>>      0xf0000, and also set other related registers/msr to the
>>>      correct value/attributes in realmode environment which will
>>>      start from rombios post Entry code in realmode directly when
>>> resuming. 
>>>   3. rombios post code will start s3 resume by jumping to wakeup   
>>> vector set by guest OS. 
>>>   4. pause domain
>>> - On resume, "xm trigger <domid> s3resume will call hypercall to
>>> trap to XEN 
>>> 
>>> How to use it:
>>> - apply this patch to changeset 17655:2ada81810ddb
>>> - create and boot HVM domain
>>> - In HVM guest, enter S3 state
>>>   * for Linux, "echo mem >/sys/power/state"
>>>   * for Windows, shutdown windows by Standby
>>> - to resume HVM domain, "xm trigger <domid> s3resume"
>>> 
>>> 
>>> 
>>> Kevin/Ke/Liping
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> 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


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