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


Re: [Xen-devel] PCI passthrough issue

Sorry for long silence: had some hollidays :)

On 16/03/2011 04:14, Konrad Rzeszutek Wilk wrote:
> On Fri, Mar 04, 2011 at 08:25:49AM +0100, Jean Baptiste Favre wrote:
>> Hello Konrad,
>> Le 03/03/2011 23:58, Konrad Rzeszutek Wilk a écrit :
>>>> I don't remember such problem. Could this module be
>>>> BTW, I'm checking that rebuilding OpenWRT.
>>> OK.
>>> To eliminate this being the kernel, I took the
>>> trunk/build_dir/toolchain-i386_gcc-linaro_uClibc-0.9.32/linux-2.6.37
>>> (which has a bunch of patches on top of stock 2.6.37)
>>> compiled it outside the OpenWRT and tried to passthrough the same
>>> adapter. It worked. But let me try to follow your directions
>>> below tomorrow and see what progress I can make.
>> Hello,
>> One tought or two between wake-up and leaving for work :-)
> I haven't gotten back on this - sorry about this.
> The other thing that might be going wrong is that CONFIG_PCI_QUIRKS is not
> turned on in the OpenWRT build. Perhaps there are some work-arounds for the
> driver that aren't enabled with OpenWRT build? You could try to
> build a debian kernel using the OpenWRT .config and seeing if
> it works right?
In my setup, CONFIG_PCI_QUIRKS is enabled. As default compilation did
not worked, I took all XEN and PCI related config options from Debian
kernel and manually added them in target/linux/x86/xen_domu/config-default

As a consequence, its activated in final kernel but with no change :(

>> trunk/build_dir/toolchain-i386_gcc-linaro_uClibc-0.9.32/linux-2.6.37
>>  is kernel builddir. So, if it works from here, there's no reason it
>> finaly doesn't.
>> One tought: in "make menuconfig", you will setup the Openwrt's
>> package/features list. If you have one package marked "M", that means
>> it'll be build as separate package (*.opkg). If marked with "y", it'll
>> be integrated within FS image.
>> For you kernel module xen-pcifront, you have to make sure that:
>> - it's marked in trunk/.config
>> - it's marked in kernel config file
>> You can check after compliation:
>> ls -l build_dir/linux-x86_xen_domu/packages/ipkg-x86/kmod-xen-pcidev/
>> total 12
>> drwxr-xr-x 2 jbfavre jbfavre 4096 Mar  4 01:09 CONTROL
>> drwxr-xr-x 3 jbfavre jbfavre 4096 Mar  4 01:09 etc
>> drwxr-xr-x 3 jbfavre jbfavre 4096 Mar  4 01:09 lib
>> jbfavre@xps-103:~/openwrt/trunk$ ls -l
>> build_dir/linux-x86_xen_domu/packages/ipkg-x86/kmod-xen-pcidev/lib/modules/2.6.37/platform-pci.ko
>> -rw-r--r-- 1 jbfavre jbfavre 4936 Mar  4 01:09
>> build_dir/linux-x86_xen_domu/packages/ipkg-x86/kmod-xen-pcidev/lib/modules/2.6.37/platform-pci.ko
>> So, not sure you patch is mandatory, is it ?
> Probably not.
> Will get back to this after the XenHackothon.
Hope this goes well :)


Xen-devel mailing list

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