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

RE: [Xen-devel] ac_timer: time to say goodbye?

  • To: "Rolf Neugebauer" <rolf.neugebauer@xxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Mon, 23 May 2005 14:07:34 -0700
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 23 May 2005 21:07:34 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcVf2KWwnjmGi8iOSQiWOl3sMTSUwgAAixmQ
  • Thread-topic: [Xen-devel] ac_timer: time to say goodbye?

> Of the top of my head:
> Each domain has a timer to schedule timeout values. So 
> depending on how many
> domains are blocking the number of timers varies.
> Then there is one timer per vcpu to generate a ticker for the 
> currently
> running VM.

Every domain or every *active* domain?

For inactive domains, determining when the next ticker
should be delivered could be part of the domain context,
with next tick scheduled when it is made active.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.