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 6/6] Add MSI support to XEN

To: "Shan, Haitao" <haitao.shan@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 6/6] Add MSI support to XEN
From: Neil Turton <nturton@xxxxxxxxxxxxxx>
Date: Tue, 13 May 2008 10:57:29 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Delivery-date: Tue, 13 May 2008 02:58:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <823A93EED437D048963A3697DB0E35DE014F156F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <823A93EED437D048963A3697DB0E35DE014F156F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.0 (X11/20070326)
I tried the latest unstable tree on a NIC which supports both MSI and
MSI-X.  When the driver was configured to use MSI mode, everything
worked fine but when it was configured to use MSI-X, the call to
pci_enable_msix succeeded but the interrupt didn't work.  Have these
patches been seen to work on an MSI-X device?

In msix_capability_init (drivers/pci/msi-xen.c), there's a loop which
unmaps the old pirqs.  Shouldn't there be some similar code in
msi_capability_init?  I can't see any reason for the inconsistency
between the two functions.

Would it be possible to extend this code so that a PV backend driver
could map different MSI-X entries on a PCI device into different guests?
We already have frontend/backend drivers which allow multiple guests to
securely access the PCI memory of a single NIC and would like to extend
those drivers to map MSI-X interrupts directly to guests.  I
still don't understand enough about the new hypercalls to see how that
would work.

Cheers, Neil.

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