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/
Home Products Support Community News


Re: [Xen-devel] PCI MSI questions

To: Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] PCI MSI questions
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 08 Aug 2008 11:18:32 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 08 Aug 2008 03:19:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <489C3769.76E4.0078.0@xxxxxxxxxx>
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: Acj5QBvRWmpwgGUzEd2xugAX8io7RQ==
Thread-topic: [Xen-devel] PCI MSI questions
User-agent: Microsoft-Entourage/
On 8/8/08 11:09, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

>> Or have the kernel remap the return value of map_pirq into its own PIRQ
>> namespace, and maintain appropriate translation info? Although, it'd be nice
>> to have dynamic NR_IRQS sizing anyway -- people who want to run lots of
>> domUs currently may have to recompile dom0 with more DYNIRQS.
> So what route would you prefer to go (so that if I'm able to get to it I
> wouldn't end up submitting a patch you'd have wanted done the other
> way around)?

I'd like the extra level of renaming. The guest shouldn't need to make
assumptions about the pirq handles handed out by Xen.

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>