From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ritu kaur <ritu.kaur.us@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: pci-passthrough and shared interrupts
Date: Wed, 25 Aug 2010 19:43:30 -0400 [thread overview]
Message-ID: <20100825234330.GA6588@phenom.dumpdata.com> (raw)
In-Reply-To: <AANLkTim_Fn8ZMHvtVBLz453cC+C7g0pqMKKj7MS_kLAm@mail.gmail.com>
On Wed, Aug 25, 2010 at 03:48:35PM -0700, Ritu kaur wrote:
> Thanks Konrad. Additional Q below
>
> On Wed, Aug 25, 2010 at 3:34 PM, Konrad Rzeszutek Wilk <
> konrad.wilk@oracle.com> wrote:
>
> > On Wed, Aug 25, 2010 at 03:17:29PM -0700, Ritu kaur wrote:
> > > Hello,
> > >
> > > Couple of months back when we were testing xcp 0.1.1 and pci passthrough
> > we
> > > ran into issues when pci-passthrough enabled device shared interrupts
> > with
> > > another controller(in our case interrupt was shared between ide
> > controller
> > > and our nic). At that time Ian Campbell suggested backporting
> > event-channel
> > > changes from pvops to 2.6.27 kernel. Have two questions related to this
> > >
> > > 1. I am thinking of porting the changes now but wanted to check if it has
> > > been addressed?
> >
> > I've added some patches in the pvops tree that make this work. You would
> > essentially have to backport the pciback driver to the XCP
> > infrastructure. And you might have to backport the event channels as
> > well, not sure about that.
> >
>
> I will take a look at the patches.
>
> > >
> > > 2. Will shared interrupts be a problem for pci-e slots as well?
> >
> > No.
> >
>
> So if I have XCP + NIC installed in pci-e slot and interrupts shared with
> another device, pci passthrough should work fine, is this correct?
Ugh, I am surprised you have that. Most of the time if you do use an NIC
in PCI-e it would be MSI based. An MSI's are never shared.
So if your device is PCIe and you get legacy IRQ that is shared with
another device on your board, then you will need to backport the
'pciback' driver.
What NIC is it that does this?
next prev parent reply other threads:[~2010-08-25 23:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 22:17 pci-passthrough and shared interrupts Ritu kaur
2010-08-25 22:34 ` Konrad Rzeszutek Wilk
2010-08-25 22:48 ` Ritu kaur
2010-08-25 23:43 ` Konrad Rzeszutek Wilk [this message]
2010-08-26 22:58 ` Ritu kaur
2010-08-27 14:03 ` Konrad Rzeszutek Wilk
2010-09-30 2:14 ` Ritu kaur
2010-09-30 6:01 ` Pasi Kärkkäinen
2010-09-30 19:07 ` Ritu kaur
2010-10-01 13:45 ` Konrad Rzeszutek Wilk
2010-10-01 15:36 ` Ritu kaur
2010-10-01 15:58 ` Konrad Rzeszutek Wilk
2010-10-03 16:07 ` Ritu kaur
2010-10-03 16:41 ` Ritu kaur
2010-10-03 16:54 ` Pasi Kärkkäinen
2010-10-03 17:12 ` Ritu kaur
2010-10-03 17:18 ` Pasi Kärkkäinen
2010-10-03 16:42 ` Ritu kaur
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=20100825234330.GA6588@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=ritu.kaur.us@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).