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] [PATCH 00 of 38] xen: add more Xen dom0 support

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: RE: [Xen-devel] [PATCH 00 of 38] xen: add more Xen dom0 support
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Tue, 24 Mar 2009 10:23:10 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 23 Mar 2009 19:24:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49C7B884.90306@xxxxxxxx>
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>
References: <patchbomb.1226603398@xxxxxxxxxxxxxxxxx> <E2263E4A5B2284449EEBD0AAB751098401CE6DEBC6@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <49C7B884.90306@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acmr1FGBh3e8F5DURaC0JWsJHnGeKgAUllwQ
Thread-topic: [Xen-devel] [PATCH 00 of 38] xen: add more Xen dom0 support
 

>-----Original Message-----
>From: Jeremy Fitzhardinge [mailto:jeremy@xxxxxxxx] 
>Sent: 2009年3月24日 0:28
>To: Jiang, Yunhong
>Cc: Xen-devel
>Subject: Re: [Xen-devel] [PATCH 00 of 38] xen: add more Xen 
>dom0 support
>
>Jiang, Yunhong wrote:
>> We are working on the MSI support now. I'd get some guide on 
>how the pirq is defined in pv dom0, can I assume it is 
>something like xen interrupt controller's gsi?
>
>
>The pirq we pass to Xen is the Linux irq we allocate for the interrupt
>source. For compatibility with native, we maintain an irq == gsi
>identity, so the Xen pirq will also equal the gsi. However, there's no
>problem in allocating irqs above the highest gsi for msi use; you could
>either adapt xen_allocate_pirq or add an msi variant. I think the first
>is preferred if possible; you'd just use "gsi" to refer to msis too, if
>they have easily distinguished identifiers.

I think both should be ok for dom0. Should the driver domain support be 
considered also now?

>
>Are you thinking of putting a Xen hook in setup_msi_irq?

Yes, exactly, I assume it is acceptable for changes under arch/x86/kernel/, 
like what changes for IOAPIC, am I right?

Thanks
Yunhong Jiang

>
>Thanks,
>J
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>