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

Re: [Xen-devel] Re: [PATCH] xen: always handle VIRQ_TIMER first.


  • To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Sun, 17 Oct 2010 08:38:35 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Campbell <ian.campbell@xxxxxxxxxx>
  • Delivery-date: Sun, 17 Oct 2010 00:39:23 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=uqqBD1YLMTf9GMEtgHmnmvPOoMjuQCRwy3ui4lSKlpkjPP7CeVTZ9OtSDprz+UbYr7 xM9LTiAPH2kqzobu+ZuiUMJA5xvbMl7dvH0KGtqE47XnHQvKnjQcfjtfxAajI0+I7UAJ xMvBXOjm7d65tqOkIu7IkNOJx1c0DGAUnfllU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acttzk4H8whPa+nV+UCxYq+GFvlhog==
  • Thread-topic: [Xen-devel] Re: [PATCH] xen: always handle VIRQ_TIMER first.

On 17/10/2010 07:11, "Jeremy Fitzhardinge" <jeremy@xxxxxxxx> wrote:

>> We fixed it the way we did in 'classic Xen' patched kernels since it seemed
>> arhitecturally neatest. I can accept that in the tickless kernel world that
>> may not actually be true.
> 
> I think (but I haven't spelunked into that code lately) that after a
> tickless idle period it will update jiffies N ticks based on the
> clocksource, and then run any other interrupt handler code, so jiffies
> will always appear to be up to date.

Okay, that should suffice. That presumably calls into the clocksource and
gives us our opportunity to sync with Xen's current system time. Effectively
it's just hooking into the interrupt handling preamble at a different, more
generic, point. :-)

 -- Keir



_______________________________________________
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®.