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

Re: [Xen-devel] irq_guest_eoi_timer interaction with MSI


  • To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Thu, 13 Nov 2008 11:22:51 +0000
  • Cc:
  • Delivery-date: Thu, 13 Nov 2008 03:23:23 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AclFgUzli0G/eLF0Ed2N7wAX8io7RQAAN0gf
  • Thread-topic: [Xen-devel] irq_guest_eoi_timer interaction with MSI

Oh yes, and indeed this could be stashed at the end of shared_info. We could
reserve another bitmap of, say, 1024 bits quite easily. Plenty of PIRQs!

 -- Keir

On 13/11/08 11:16, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> wrote:

> We already have PHYSDEVOP_eoi. We can force guests to always use that. It'll
> be no slower than level-triggered IO-APIC IRQs, which we've been using since
> forever with no complaints. And yeah, as an extension we could have a
> shared-memory pirq bitmap to indicate dynamically whether eoi is required.
> Quite a secondary concern though, I would say.



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