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

[Xen-devel][PATCH]Fix the issue of Dom0's multiple S3 failure. Improve accuracy of time offset calculation in S3.


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx>
  • Date: Fri, 25 Jan 2008 11:51:54 +0800
  • Delivery-date: Thu, 24 Jan 2008 19:53:08 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AchfBK+eBGkiO3UITzyS5XtvidPZWwAABDyQAAAw59A=
  • Thread-topic: [Xen-devel][PATCH]Fix the issue of Dom0's multiple S3 failure. Improve accuracy of time offset calculation in S3.

Fix the issue: Dom0-S3 will fail after sleep-wake for several times.
  -Time zone info just needs to be calculated in S3 suspend procedure.
However, time_suspend() is also called on AP. That wasteful
get_cmos_time() on AP may break __cpu_die() assumption since
get_cmos_time() can take up to one second. This fix just limits it on
BSP.

Improve accuracy of the cmos_utc_offset calculation.
  -The get_cmos_time() function may take up to 1 second, while execution
of the NOW() macro could be very fast. So when calculating
cmos_utc_offset, get_cmos_time() should be firstly executed, and then 
(wc_sec + (wc_nsec + NOW()) / 1000000000ULL). 
This would make the calculation more accuracy than vice versa.

Signed-off-by: Xu Dongxiao <dongxiao.xu@xxxxxxxxx>

Attachment: multi-s3.patch
Description: multi-s3.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®.