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

[Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Mon, 27 Sep 2010 08:52:39 -0700
Delivery-date: Mon, 27 Sep 2010 08:53:20 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=DwzdmkduiDAVReNDb5isQCxFH8PwQGGhrEul7Y/OAQk=; b=apvPaIcP/NHRnn69K7UaeANdcsi8Xn7DxvY0rX7XMqf0uzSmyLCDX7OaxnpHd4zaPS 9+e63hIWEQN74ZSg+X3l9w+WLsOVrq/GjZkaoxmQU8XDeTeHW2w662638XnIUXbTi+V9 v3TFwTCUPakuC6dBpDOD5dsRCzdYUE5Q0rsbw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=lhztWpEAdEBH6magMLv3CLfz3m0NNcubsW9pHP0PAotKKfBb8jX0F0wy49sTe+1OTI E0k47aTynHgqrpsSonUFl5aV2sS5BCdubeA0UZH5Kiqw1HyoMSsQPxl5E8yGhKUKXoYu nE+klyM4iHC6awa6/J+unVvmIoKHS6Qf+s+Xg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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
- 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

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


-Bruce

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