WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Multiple IRQ's in HVM for Windows
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 26 Dec 2008 10:36:25 +0000
Cc:
Delivery-date: Fri, 26 Dec 2008 02:36:53 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D015500E2@trantor>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclnCjPkeAYvm5WbTaqM+PmGGNFiHQAIdYQ3AAU6BeAAATbLsQ==
Thread-topic: [Xen-devel] Multiple IRQ's in HVM for Windows
User-agent: Microsoft-Entourage/12.15.0.081119
On 26/12/2008 10:15, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel