All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Lin, Ray" <Ray.Lin@lsi.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Bruce Edge <bruce.edge@gmail.com>
Subject: Re: pv-ops domU not working with MSI interrupts on Nehalem
Date: Fri, 8 Oct 2010 13:30:54 -0400	[thread overview]
Message-ID: <20101008173054.GA20884@dumpdata.com> (raw)
In-Reply-To: <EB4C61A1A2501842A04B573FE42B14D60131955797@cosmail02.lsi.com>

On Fri, Oct 08, 2010 at 10:48:01AM -0600, Lin, Ray wrote:
> 
> I just tried Bruce's latest kernel build based on Konrad's devel/xen-pcifront-0.7. It doesn't help the issue we have. The driver still doesn't recognize the source of interrupt, even though the interrupts happen.
> 
> 
> 124:      87792          0          0          0          0          0      12208          0          0          0          0          0          0          0  xen-pirq-pcifront-msi  HW_TACHYON
> 125:      89692          0          0          0      10308          0          0          0          0          0          0          0          0          0  xen-pirq-pcifront-msi  HW_TACHYON
> 126:      90979          0       9021          0          0          0          0          0          0          0          0          0          0          0  xen-pirq-pcifront-msi  HW_TACHYON
> 127:     100000          0          0          0          0          0          0          0          0          0          0          0          0          0  xen-pirq-pcifront-msi  HW_TACHYON
> 

And you still get on the Xen hypervisor side the DMAR failure of reading the memory?

  reply	other threads:[~2010-10-08 17:30 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 15:52 pv-ops domU not working with MSI interrupts on Nehalem Bruce Edge
2010-09-27 17:24 ` 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 [this message]
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=20101008173054.GA20884@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ray.Lin@lsi.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.