From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Multiple IRQ's in HVM for Windows Date: Fri, 26 Dec 2008 10:36:25 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: James Harper , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 26/12/2008 10:15, "James Harper" wrote: > The above probably shows a lack of understanding on my part about how > events are delivered into hvm domains as interrupts - can you point me > to what files I need to look at to understand this better? Then maybe > I'll have a better idea about what I'm asking for (or I'll understand > why it won't work :) Currently all event channels are tied together as a single interrupt line, which can be configured to appear to come from the xen-platform fake PCI device. We could duplicate that device so you could have a PCI INTx line per CPU. Or duplicate it so that you could have a PCI INTx line per event channel (or at least barber-pole onto such a set of INTx lines). Or we could bypass the INTx emulation entirely, and deliver per-cpu event_pending status to that HVM VCPU's local APIC, on a pre-registered interrupt vector (this is most like MSI, except the interrupt wouldn't be coming from a PCI device, although we could perhaps even fake that out too). There's quite a few options. -- Keir