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@xxxxxxxxx) in the
future
who is right now on travel and he might have better suggestions. CC-ing him on
this e-mail.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home