xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bruce Edge <bruce.edge@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: pv-ops domU not working with MSI interrupts on Nehalem
Date: Tue, 28 Sep 2010 10:56:16 -0400	[thread overview]
Message-ID: <20100928145616.GA11328@dumpdata.com> (raw)
In-Reply-To: <AANLkTikqCk0wYwJaSygy-yF5q5k+b1EqrKUOZA4nWTTj@mail.gmail.com>

>  git clone  git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> 
> Initialized empty Git repository in
> /import/kaan/bedge/src/xen/kernel/pv-ops/xen/.git/
> remote: error: Could not read 59eab2f8f04147c5aadc99f2034ca7e5b81e890f
> remote: fatal: Failed to traverse parents of commit
> 979e121cb348add17ed8171bf447b27a3a9d1be3
> remote: aborting due to possible repository corruption on the remote side.
> fatal: early EOF
> fatal: index-pack failed

That should have worked, but it looks as my git repo is busted. Let me fix that
and once it done you should be able to do

cd xen
git checkout origin/pv/pcifront-2.6.32

> 
> >
> > It has the latest pcifront driver but without the PVonHVM enhancments
> > so we can try to eliminate the PvONHVM logic out of the picture.
> >
> >>
> >> >
> >> > > - 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?
> >> >
> >>
> >> The driver would check the appropriate register (tachyon registers) in
> >> the MMIO to determine the source of interrupts.
> >
> > OK, so that isn't it. Is there anything at these vectors:
> > 7c, 7d, 7e, and 7f? When you use xen debug-keys 'i' or 'q' it should give you
> > an inkling what device this is set for.
> 
> When I run a distro kernel in hvm mode, I get the expected irq mappings:
> 
> 'i' - Note 66 - 69
> (XEN)    IRQ:  66 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:3a
> type=PCI-MSI         status=00000010 in-flight=0
> domain-list=10:127(----),
> (XEN)    IRQ:  67 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:42
> type=PCI-MSI         status=00000010 in-flight=0
> domain-list=10:126(----),
> (XEN)    IRQ:  68 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:4a
> type=PCI-MSI         status=00000010 in-flight=0
> domain-list=10:125(----),
> (XEN)    IRQ:  69 affinity:ffffffff,ffffffff,ffffffff,ffffffff vec:52
> type=PCI-MSI         status=00000010 in-flight=0
> domain-list=10:124(----)
> 

What does cat /proc/interrupts (don't do the grep) for this HVM guest?
> 
> 'q'
> (XEN)     Interrupts { 32, 41-42, 47, 124-127 }

  parent reply	other threads:[~2010-09-28 14:56 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 [this message]
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=20100928145616.GA11328@dumpdata.com \
    --to=konrad.wilk@oracle.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 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).