xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Edge <bruce.edge@gmail.com>
To: xen-devel@lists.xensource.com
Subject: pv-ops domU not working with MSI interrupts on Nehalem
Date: Mon, 27 Sep 2010 08:52:39 -0700	[thread overview]
Message-ID: <AANLkTi=G7CTuVP2=b18JjwFsCb_fvk8hoMWAngYUKB1Y@mail.gmail.com> (raw)

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

             reply	other threads:[~2010-09-27 15:52 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 15:52 Bruce Edge [this message]
2010-09-27 17:24 ` pv-ops domU not working with MSI interrupts on Nehalem Konrad Rzeszutek Wilk
2010-09-27 19:16   ` Bruce Edge
2010-09-27 19:54     ` Konrad Rzeszutek Wilk
2010-09-27 23:54       ` Bruce Edge
2010-09-28  1:15         ` Jiang, Yunhong
2010-09-28  3:16           ` Bruce Edge
2010-09-28  3:26             ` Jiang, Yunhong
2010-09-28  4:45               ` Bruce Edge
2010-09-28 16:08                 ` Lin, Ray
2010-09-28 16:19                   ` Konrad Rzeszutek Wilk
2010-09-28 18:35                     ` Lin, Ray
2010-09-28 20:14                       ` Konrad Rzeszutek Wilk
2010-09-28 20:38                         ` Lin, Ray
2010-09-29  0:53                     ` Jiang, Yunhong
2010-09-30 16:30                       ` Lin, Ray
2010-09-28 14:56         ` Konrad Rzeszutek Wilk
2010-09-30 18:55           ` Bruce Edge
2010-10-01 21:11 ` Konrad Rzeszutek Wilk
2010-10-01 21:19   ` Bruce Edge
2010-10-01 23:30   ` Bruce Edge
2010-10-03  5:46     ` Bruce Edge
2010-10-03 12:08       ` Pasi Kärkkäinen
2010-10-04 14:48     ` Konrad Rzeszutek Wilk
2010-10-05 18:21       ` Bruce Edge
2010-10-06 14:21         ` Konrad Rzeszutek Wilk
2010-10-06 18:21           ` Bruce Edge
2010-10-08 16:48             ` Lin, Ray
2010-10-08 17:30               ` Konrad Rzeszutek Wilk
2010-10-08 17:40                 ` Lin, Ray
2010-10-08 17:52                 ` Bruce Edge
2010-10-08 21:01                   ` Lin, Ray
2010-10-08 17:56   ` Bruce Edge
2010-10-11 21:12   ` Bruce Edge
2010-10-11 21:46     ` Konrad Rzeszutek Wilk
2010-10-13 21:36       ` Bruce Edge
2010-10-13 21:46         ` Konrad Rzeszutek Wilk
2010-10-13 22:00           ` Bruce Edge
2010-10-13 22:08             ` Bruce Edge
2010-10-14 13:57               ` Konrad Rzeszutek Wilk
  -- strict thread matches above, loose matches on Subject: below --
2010-09-28 23:25 Lin, Ray
2010-09-28 23:57 ` Konrad Rzeszutek Wilk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=G7CTuVP2=b18JjwFsCb_fvk8hoMWAngYUKB1Y@mail.gmail.com' \
    --to=bruce.edge@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).