From: Konrad Rzeszutek Wilk <konrad.wilk@Oracle.Com>
To: Nick Couchman <Nick.Couchman@seakr.com>, weidong.han@intel.com
Cc: xen-devel@lists.xensource.com
Subject: Re: PCI Passthrough Problems/Questions
Date: Mon, 25 Oct 2010 15:07:52 -0400 [thread overview]
Message-ID: <20101025190752.GB6452@dumpdata.com> (raw)
In-Reply-To: <4CC57D2102000099000BA6E6@collaborate.seakr.com>
On Mon, Oct 25, 2010 at 12:50:41PM -0600, Nick Couchman wrote:
> On Mon, 2010-10-25 at 14:48 -0400, Konrad Rzeszutek Wilk wrote:
> > On Mon, Oct 25, 2010 at 12:33:09PM -0600, Nick Couchman wrote:
> > > On Mon, 2010-10-25 at 13:40 -0400, Konrad Rzeszutek Wilk wrote:
> > >
> > > >
> > > > What do you see on your Xen serial output? I presume you cranked up logging:
> > > > loglevel=all guest_lvl=all iommu=verbose on your Xen command line.
> > > >
> > > > Is there anything that shows up when you get the 'Failed to assign.." ?
> > > >
> > >
> > > The only messages I get on the serial console after setting those
> > > parameters on the xen.gz kernel line in grub (and rebooting, of course)
> > > are the following:
> > >
> > > (XEN) [VT-D]iommu.c:1496: d0:PCI: unmap bdf = 2:0.0
> > > (XEN) [VT-D]iommu.c:1364: d1:PCI: map bdf = 2:0.0
> > > (XEN) domctl.c:848:d0 XEN_DOMCTL_assign_device: assign device (2:0.0)
> > > failed
> > > (XEN) event_channel.c:192:d0 EVTCHNOP failure: domain 1, error -22
> >
> > So, -EINVAL. How comfortable are you sticking a bunch of
> > dprintk(VTDPREFIX, " in the drivers/passthrough/vtd/iommu.c file? Basically
> > you need to figure which of the functions that are past line 1364
> > are being called and return -EINVAL.
>
> I'm happy to give it a shot...it'll take a while to get the devel
> environment configured, as I'm using packages right now and I don't even
> think I have a compiler on this system. I'll report back once I get
> that done and give that a try.
Excellent. You might also want to CC Weidong (weidong.han@intel.com) in the future
who is right now on travel and he might have better suggestions. CC-ing him on this e-mail.
next prev parent reply other threads:[~2010-10-25 19:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 16:35 PCI Passthrough Problems/Questions Nick Couchman
2010-10-25 17:40 ` Konrad Rzeszutek Wilk
2010-10-25 18:33 ` Nick Couchman
2010-10-25 18:48 ` Konrad Rzeszutek Wilk
2010-10-25 18:50 ` Nick Couchman
2010-10-25 19:07 ` Konrad Rzeszutek Wilk [this message]
2010-10-25 19:45 ` Nick Couchman
2010-10-25 20:11 ` Nick Couchman
2010-10-27 6:40 ` Weidong Han
2010-10-27 15:07 ` Nick Couchman
2010-10-28 2:31 ` Weidong Han
[not found] <4CC8A62602000099000BAA42@collaborate.seakr.com>
2010-10-28 4:37 ` Han, Weidong
-- strict thread matches above, loose matches on Subject: below --
2010-10-28 14:01 Nick Couchman
2010-10-29 2:54 ` Weidong Han
2010-10-29 18:52 ` Nick Couchman
2010-11-02 3:30 ` Weidong Han
2010-11-02 19:07 ` Nick Couchman
2010-11-03 1:01 ` Weidong Han
2010-11-03 14:54 ` Nick Couchman
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=20101025190752.GB6452@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Nick.Couchman@seakr.com \
--cc=weidong.han@intel.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.