This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [pvops xen/next ][iommu] attenpt to passthrough PCI-e us

To: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [pvops xen/next ][iommu] attenpt to passthrough PCI-e usb controllor to PV domU SUCCESS :-)
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 22 Mar 2010 16:30:18 -0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Han, Weidong" <weidong.han@xxxxxxxxx>
Delivery-date: Mon, 22 Mar 2010 14:02:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1609670718.20100322213550@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1017192770.20100321221949@xxxxxxxxxxxxxx> <1A42CE6F5F474C41B63392A5F80372B21D641D6D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1057357311.20100322111524@xxxxxxxxxxxxxx> <20100322191237.GB31521@xxxxxxxxxxxxxxxxxxx> <1609670718.20100322213550@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Mon, Mar 22, 2010 at 09:35:50PM +0100, Sander Eikelenboom wrote:
> Hi Konrad,
> Thx again and again and again :-)

Oh nice. Glad to hear.

> Works like a charm by adding these to the domU kernel options.
> I saw a lot of your hard work on the swiotlb on LKML as well, would be nice 
> if it would be accepted together with pci-front,
> that would make mainline kernels as domU work with pci-passthrough as well.

Yes!  That is the idea - to have the xen-pcifront upstream. Thought as
you experienced first hand, first the SWIOTLB need to be in the kernel
to make the PCI front patches work.
> I now got it running with the linux 2.6.33 tree from your git tree, which is 
> of course also very recent :-)

Oh boy. You are adventurous :-) .. 
> Now running on:
> hypervisor: xen-4.0.0-rc6
> dom0: xen-next
> domU: 2.6.33 tree with pcifront and swiotlb from Konrad's git tree, and with 
> some additional patches to het isochronous URB's working on the USB 3.0 xHCI 
> driver from linux-usb mailing lists.
> Pasi, perhaps a good thing to point out in the passthrough wiki pages (at 
> least when using pvops kernels),

Well, in regards to those trees of mine I keep on reworking them so that they 
will be
ready for upstream. They don't have all of the nice bells and whistles
that xen/next has - just the basics to get xen-pcifront working.

> BTW how do you handle tables in the wiki's ?
> Because i tried with the xen-hypervisor-boot-options page, but it was a real 
> pain in the *ss to set it up.
> --
> Sander
> Monday, March 22, 2010, 8:12:37 PM, you wrote:
> > On Mon, Mar 22, 2010 at 11:15:24AM +0100, Sander Eikelenboom wrote:
> >> Hello Weidong/Konrad,
> >> 
> >> 1) With iommu=0, the DMAR fault is gone (of course), but
> >>         > (XEN) traps.c:2309:d1 Domain attempted WRMSR 000000000000008b 
> >> from 00000a07:00000000 to 00000000:00000000.
> >>         Stays in xm-dmesg, the pv guests is booted, and lspci shows the 
> >> pci device. But the device doesn't function properly.
> > How does it not function properly? Was this related to the IOMMU error ?
> > Did you point it out to me previously and I missed it? If so, can you
> > resend it to me please.
> > If the problem is with the message about needing 'swiotlb=force' to be
> > passed, 'iommu=soft swiotlb=force' should take care of that. 
> -- 
> Best regards,
>  Sander                            mailto:linux@xxxxxxxxxxxxxx

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>