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>
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 27 Sep 2010 13:24:34 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 27 Sep 2010 10:25:54 -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.
> 
> Here are his comments:
> 
> - the driver has no problem to enable msi interrupt and request the
> interrupt through kernel functions pci_enable_msi & request_irq

What shows up in the Xen console when you send the 'q' key? Does it
show that the vector is assigned to the appropiate guest?

> - the interrupt does happen. But the interrupt service routine of
> tachyon driver doesn't detect any interrupt status related to this
> interrupt, which inhibits the tachyon chip from coming on-line. And
> there are high count of tachyon interrupt in /proc/interrupts

Is it checking the PCI_STATUS_INTERRUPT or the appropiate register
in the MMIO BAR?

> 
> kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> 124:     760415          0          0          0          0          0
>          0          0          0          0          0          0
>     0          0  xen-pirq-pcifront-msi  HW_TACHYON
> 125:     762234          0          0          0          0          0
>          0          0          0          0          0          0
>     0          0  xen-pirq-pcifront-msi  HW_TACHYON
> 126:     764180          0          0          0          0          0
>          0          0          0          0          0          0
>     0          0  xen-pirq-pcifront-msi  HW_TACHYON
> 127:     764164          0          0          0          0          0
>          0          0          0          0          0          0
>     0          0  xen-pirq-pcifront-msi  HW_TACHYON

Can you provide the full dmesg output?

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