From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@Oracle.Com>
Subject: Re: pv-ops domU not working with MSI interrupts on Nehalem
Date: Mon, 27 Sep 2010 13:24:34 -0400
Message-ID: <20100927172434.GA5957@dumpdata.com>
References: <AANLkTi=G7CTuVP2=b18JjwFsCb_fvk8hoMWAngYUKB1Y@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <AANLkTi=G7CTuVP2=b18JjwFsCb_fvk8hoMWAngYUKB1Y@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Bruce Edge <bruce.edge@gmail.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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.
>=20
> Here are his comments:
>=20
> - 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?

>=20
> kaan-18-dpm:~# cat /proc/interrupts | grep TACH
> 124: =A0 =A0 760415 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0=
 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00
> =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =
=A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00
>  =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0xen-pirq-pcifront-msi =A0HW_TACHYON
> 125: =A0 =A0 762234 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0=
 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00
> =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =
=A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00
>  =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0xen-pirq-pcifront-msi =A0HW_TACHYON
> 126: =A0 =A0 764180 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0=
 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00
> =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =
=A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00
>  =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0xen-pirq-pcifront-msi =A0HW_TACHYON
> 127: =A0 =A0 764164 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0=
 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00
> =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =
=A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A00
>  =A0 =A00 =A0 =A0 =A0 =A0 =A00 =A0xen-pirq-pcifront-msi =A0HW_TACHYON

Can you provide the full dmesg output?