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

[Xen-devel] About pit irq


  • To: 'Keir Fraser' <keir.fraser@xxxxxxxxxxxxx>, 'xen-devel' <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Wed, 19 Nov 2008 10:01:17 +0800
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • Cc:
  • Delivery-date: Tue, 18 Nov 2008 18:01:51 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AclJ6rZmkfZkqKK6QNCPP6epkry8AQ==
  • Thread-topic: About pit irq

Currently pit irq is enabled when using pit as clocksource or 
taking pit as broadcast means for deep C-state. I'm curious
whether pit irq is really required for the 1st case. When pit
is chosen as clocksource, 10ms periodical pit interrupt converts
16 counter into monotonic 32bit stamp, and then ~27ms platform 
overflow timer converts 32bit into 64bit stamp. Is the first
conversion really necessary? platform overflow timer is chosen
as 1/2 period, and it looks safe enough to convert from 16bit
into 64bit stamp directly. Just one special bit to indicate
whether counter counts down or up.

Thanks,
Kevin
_______________________________________________
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®.