[Xen-devel] Re: [pvops xen/next ][iommu] attenpt to passthrough PCI-e usb controllor to PV domU SUCCESS :-)

[Sander Eikelenboom <linux@xxxxxxxxxxxxxx>]

Hi Konrad,

Thx again and again and again :-)
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.

I now got it running with the linux 2.6.33 tree from your git tree, which is of 
course also very recent :-)

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),
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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel