RE: [Xen-devel] RE: Weird NOW() values after host S3 resume

["Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx>]

Or you may port Xen C/S 16688 and 16882 to your tree and see if this issue 
still exists. :-)

Best regards,
-- Dongxiao

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Xu, Dongxiao
Sent: 2008年5月22日 10:50
To: Guy Zana; xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: Tian, Kevin
Subject: [Xen-devel] RE: Weird NOW() values after host S3 resume

Hi, Guy
    Could you have a try of the latest Xen-unstable tree to see if this issue 
still exists? I remember some S3 time patches are added after Xen-3.2 stable 
release. 

Thanks!
-- Dongxiao

________________________________________
From: Guy Zana [mailto:guy@xxxxxxxxxxxx] 
Sent: 2008年5月22日 0:09
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: Tian, Kevin; Xu, Dongxiao
Subject: Weird NOW() values after host S3 resume

Hi all,

It seems that something is messed up with the calibration of the TSCs after 
resuming from sleep.

First, after resume NOW() issued from CPU0 gives a value that is much lower 
than before sleep, and it is probably returned to the same (default?) value 
after each resume.
Second, after each resume there is an increased differences between CPU0 and 
CPU1 NOW() values, I'm not really sure about this one because I didn't tried to 
sync my test against the HPET so take that into consideration.

Can you check this out please?

The chipset is Intel GM965/ICH8, the cpu is T7300.
Observed in Xen 3.2 stable release.

Thanks,
Guy.

_______________________________________________
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