From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: PCI passthrough issue Date: Tue, 15 Mar 2011 23:14:11 -0400 Message-ID: <20110316031411.GA7905@dumpdata.com> References: <4D5EE125.6040208@jbfavre.org> <20110225144035.GA7228@dumpdata.com> <4D6B9285.9090903@jbfavre.org> <20110228150141.GD10846@dumpdata.com> <4D6BBC70.5070109@jbfavre.org> <4D6CB851.40103@jbfavre.org> <20110303221247.GA12175@dumpdata.com> <4D701A99.10207@jbfavre.org> <20110303225803.GA19745@dumpdata.com> <4D7093FD.4040602@jbfavre.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <4D7093FD.4040602@jbfavre.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, Mar 04, 2011 at 08:25:49AM +0100, Jean Baptiste Favre wrote: > Hello Konrad, >=20 > Le 03/03/2011 23:58, Konrad Rzeszutek Wilk a =E9crit : > >> I don't remember such problem. Could this module be > >> > >> BTW, I'm checking that rebuilding OpenWRT. > >=20 > > OK. > >=20 > > To eliminate this being the kernel, I took the > >=20 > > 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) > >=20 > > 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 no= t turned on in the OpenWRT build. Perhaps there are some work-arounds for t= he 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? >=20 > 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. >=20 > 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. >=20 > 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 >=20 > 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/modu= les/2.6.37/platform-pci.ko >=20 > -rw-r--r-- 1 jbfavre jbfavre 4936 Mar 4 01:09 > build_dir/linux-x86_xen_domu/packages/ipkg-x86/kmod-xen-pcidev/lib/modu= les/2.6.37/platform-pci.ko >=20 > So, not sure you patch is mandatory, is it ? Probably not. Will get back to this after the XenHackothon. >=20 > Regards, > JB >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel