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

[Xen-devel] [PATCH 1/4] xen interface for HVM S3


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ke, Liping" <liping.ke@xxxxxxxxx>
  • Date: Thu, 8 May 2008 16:30:14 +0800
  • Cc: "Ke, Liping" <liping.ke@xxxxxxxxx>
  • Delivery-date: Thu, 08 May 2008 01:30:58 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AciwyxhLScrmK1mnQHmjBhJEDrbGSQAABwZgAAKJ6RA=
  • Thread-topic: [PATCH 1/4] xen interface for HVM S3

Hi, all
Some comments about test:
Tested the four patch under following HVM image, based on cs17589
1. Fc6 32/32e guest with both txt/X windows mode, no-vtd.
2. Fc6 32/32e guest with both txt/X windows mode, vtd-enabled, 
   assign one network card to the guest.
3. Fc5 32e HVM guest with PV driver, both txt/x windows mode.
It works fine. Test including little stress test, 
such as S3 several times.
Thanks& Regards,
Criping


[PATCH 1/4] xen interface for HVM S3
  - add two sub hypercalls under HVMOP hypercall:
    HVMOP_s3_suspend/HVM_s3_resume
  - HVMOP_s3_suspend will reset all HVM vcpus; meanwhile, power off all
    the HVM virtual device in hypervisor, e.g, pic, apic, RTC and HPET
  - HVMOP_s3_resume will set BSP eip to 0xfff0, cs base to 0xf0000, and 
    also set other registers/msr to the correct value/attributes in real
    mode environment, so HVM will start from rombios post entry directly; 
    meanwhile, power on the HVM virtual device.
Signed-off-by: Tian Kevin <kevin.tian@xxxxxxxxx>
Signed-off-by: Yu Ke <ke.yu@xxxxxxxxx>
Signed-off-by: Ke Liping <liping.ke@xxxxxxxxx>

 

Attachment: xen.patch
Description: xen.patch

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