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] Re: [PATCH 0/5] Add MSI support to xen environment

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Re: [PATCH 0/5] Add MSI support to xen environment
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Tue, 30 Oct 2007 22:27:26 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 30 Oct 2007 07:33:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C347C096.17832%Keir.Fraser@xxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <391BF3CDD2DC0848B40ACB72FA97AD590258DACF@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C347C096.17832%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgXJpgKtuetZtZRSk2SPUOVajTGGQAieFwCAArETtAAAMMrGwAAXpSgAABdVMgAx7cvwA==
Thread-topic: [Xen-devel] Re: [PATCH 0/5] Add MSI support to xen environment
So, Keir, how about the attached method for the per-domain pirq?
Now there is no need to change domain0 any more. Also domain U can't do
the map. I verified current domain0/domU works on it.
But it still changes the control panel and hope that is acceptable.

Thanks
Yunhong Jiang

xen-devel-bounces@xxxxxxxxxxxxxxxxxxx <> wrote:
> On 26/10/07 16:02, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
> 
>>> dom0 needs to be involved, since we can't let domU map any arbitrary
>>> vector into its pirq space. Since dom0 has to be involved in access
>>> control to the irq vector space, can't it do the mapping?
>> 
>> yes, what I mean is, "before starting the domain" works for IOAPIC
IRQ,
>> not MSI. MSI will still through communcation between PCI
>> frontend/backend directly.
> 
> Oh, I see. Then it probably has to be a phydevop and let dom0 kernel
do it.
> But there should be no reason to let domU use the map_irq physdev_op
at all.
> 
> -- Keir
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

Attachment: pirq_per_domain.patch
Description: pirq_per_domain.patch

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