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] pv-ops domU not working with MSI interrupts on Nehalem

To: Bruce Edge <bruce.edge@xxxxxxxxx>, Ray.Lin@xxxxxxx
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Fri, 1 Oct 2010 17:11:11 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 01 Oct 2010 14:12:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTi=G7CTuVP2=b18JjwFsCb_fvk8hoMWAngYUKB1Y@xxxxxxxxxxxxxx>
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: <AANLkTi=G7CTuVP2=b18JjwFsCb_fvk8hoMWAngYUKB1Y@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Mon, Sep 27, 2010 at 08:52:39AM -0700, Bruce Edge wrote:
> One of our developers who is working on a tachyon driver is
> complaining that the pvops domU kernel is not working for these MSI
> interrupts.
> This is using the current head of xen/2.6.32.x on both a single
> Nahelam 920 and a dual E5540. This behavior is consistent with Xen
> 4.0.1, 4.0.2.rc1-pre and 4.1.


I just checked on my SuperMicro X8DTN, this combination
 - For Dom0, git commit fe999249 (2.6.32.18)
 - For DomU, devel/xen-pcifront-0.6 or devel/xen-pcifront-0.7
 - For Hypervisor I used cs 21976, but found that the latest (22155) works too

with which where I passed in PCI devices with legacy IRQ, MSI, and MSI-X. I 
tried
a combination of doing this with IOMMU (VT-d) and without - both cases these 
devices:

00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 02)
03:00.0 Ethernet controller: Intel Corporation 82572EI Gigabit Ethernet 
Controller (Copper) (rev 06)
0a:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network 
Connection (rev 02)

worked just fine (either defining pci=["..."] or just using pci-attach).
 
But if I use the latest xen/next or xen/stable-2.6.32.x it does not look
that happy :-(


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