xen-devel
Re: [Xen-devel] Re: APIC rework
To: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
Subject: |
Re: [Xen-devel] Re: APIC rework |
From: |
Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> |
Date: |
Mon, 30 Nov 2009 09:26:34 -0500 |
Cc: |
Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Han, Weidong" <weidong.han@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> |
Delivery-date: |
Mon, 30 Nov 2009 06:27:24 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<4B0D8206.6030001@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: |
<706158FABBBA044BAD4FE898A02E4BC201CD3207E0@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C72970BC.C323%keir.fraser@xxxxxxxxxxxxx> <706158FABBBA044BAD4FE898A02E4BC201CD3A074E@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20091124194401.GA29566@xxxxxxxxxxxxxxxxxxx> <4B0C6DBA.8060100@xxxxxxxx> <20091125141014.GB2586@xxxxxxxxxxxxxxxxxxx> <4B0D8206.6030001@xxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mutt/1.5.19 (2009-01-05) |
>
> I don't particularly object to xenbus_walk per-se, its just that I don't
> think xen_create_msi_irq() should call it directly. It would be OK for
> xen_setup_msi_irqs() to call it and pass the results into
> xen_create_msi_irq().
>
> Would a registration list be any cleaner? Presumably you'd just keep a
> list of devices being controlled by other domains, so non-presence on
> the list means DOMID_SELF, so you'd only need to worry about
> registration on pciback paths. If that could be done without needing to
> touch common code (or do the horrible hacks that some of the earlier MSI
> patches did), then maybe its worthwhile.
I think that would work nicely. Should have a patch cooked up shortly
after I am done with the xen-fbfront drier in DomU.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- RE: [Xen-devel] Re: APIC rework, (continued)
- RE: [Xen-devel] Re: APIC rework, Jiang, Yunhong
- RE: [Xen-devel] Re: APIC rework, Zhang, Xiantao
- Re: [Xen-devel] Re: APIC rework, Keir Fraser
- RE: [Xen-devel] Re: APIC rework, Zhang, Xiantao
- Re: [Xen-devel] Re: APIC rework, Jeremy Fitzhardinge
- RE: [Xen-devel] Re: APIC rework, Zhang, Xiantao
- Re: [Xen-devel] Re: APIC rework, Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: APIC rework, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: APIC rework, Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: APIC rework, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: APIC rework,
Konrad Rzeszutek Wilk <=
- RE: [Xen-devel] Re: APIC rework, Zhang, Xiantao
- Re: [Xen-devel] Re: APIC rework, Konrad Rzeszutek Wilk
- RE: [Xen-devel] Re: APIC rework, Zhang, Xiantao
- Re: [Xen-devel] Re: APIC rework, Konrad Rzeszutek Wilk
- RE: [Xen-devel] Re: APIC rework, Zhang, Xiantao
- Re: [Xen-devel] Re: APIC rework, Konrad Rzeszutek Wilk
- Re: [Xen-devel] Re: APIC rework, Jeremy Fitzhardinge
- RE: [Xen-devel] Re: APIC rework, Zhang, Xiantao
- Re: [Xen-devel] Re: APIC rework, Konrad Rzeszutek Wilk
- RE: [Xen-devel] Re: APIC rework, Zhang, Xiantao
|
|
|