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

RE: [Xen-devel] Multiple IRQ's in HVM for Windows


  • To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Sun, 28 Dec 2008 14:22:43 +1100
  • Cc:
  • Delivery-date: Sat, 27 Dec 2008 19:23:20 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AclnCjPkeAYvm5WbTaqM+PmGGNFiHQAIdYQ3AAU6BeAAATbLsQAADYFAAADLT9kALf9OEAABLL7gAAAL4JAAAN6snAAABoKQAADccJAAAAwiEAAAhgyJACL03EA=
  • Thread-topic: [Xen-devel] Multiple IRQ's in HVM for Windows

> On 27/12/2008 10:28, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> 
> > Well... the 'old' way would probably still have to work (or would
it?),
> > so we could just keep allocating IRQ's until we run out and any
leftover
> > devices just have to use the old way.
> 
> Yes, that did occur to me. Might be a nice fallback while still
allowing
> up
> to 16 or whatever devices to have their interrupts distributed across
> VCPUs.
> The old mechanism does still need to work, so making it a fallback in
this
> new mechanism would be probably not too difficult.

I've been reading up on APIC's, and it appears that (depending on the
model) they can support up to 64 interrupts. Is the emulated APIC under
Xen of the 16 interrupt variety?

James

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