From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: PCI Passthrough Problems/Questions Date: Mon, 25 Oct 2010 14:48:18 -0400 Message-ID: <20101025184818.GA6259@dumpdata.com> References: <4CC55D5C02000099000BA698@collaborate.seakr.com> <20101025174033.GA5766@dumpdata.com> <4CC5790502000099000BA6DC@collaborate.seakr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4CC5790502000099000BA6DC@collaborate.seakr.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Nick Couchman Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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.