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

[Xen-devel] [PATCH] Move RTC from Qemu to HV


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Yang, Xiaowei" <xiaowei.yang@xxxxxxxxx>
  • Date: Tue, 26 Sep 2006 23:05:14 +0800
  • Delivery-date: Tue, 26 Sep 2006 08:05:47 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcbhfSgZ1zf5Dd22R7mr0rlT/3Bpdw==
  • Thread-topic: [PATCH] Move RTC from Qemu to HV

As we know some version of Windows (e.g 32bit Vista and 64bit Win2k3)
use RTC as main periodic timer at 64HZ. Currently RTC is in Qemu which
means its irq may be potentially lost due to Qemu not got scheduled on
time. And it's not sync with Guest TSC (adjusted by TSC_OFFSET). This
will cause many problems, like HVM time goes slow; TSC can't be measured
by cross referring to RTC time. 
This patch moves RTC from Qemu to HV, to resolve these problems. Since
we still need Qemu to fill out RTC ram with (local)time, fd/hd
information, HV will copy this ram from Qemu at startup and then
maintains it by itself. 
Another issue resolved by this patch is Windows which use RTC as
periodic timer hangs at login screen because there are no resources to
wait it up after it calls halt. After moving, RTC timer will wake it. 
One extra benefit is that Vista responses faster. It can be explained by
fewer IO port access cost and more accurate RTC time, which Vista may
use to refresh screen.

Thanks, 
Xiaowei 


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