From: Jean Baptiste Favre <xen-devel@jbfavre.org>
To: xen-devel@lists.xensource.com
Subject: Re: PCI passthrough issue
Date: Fri, 25 Mar 2011 14:06:11 +0100 [thread overview]
Message-ID: <4D8C9343.4060801@jbfavre.org> (raw)
In-Reply-To: <20110316031411.GA7905@dumpdata.com>
Hello,
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 :)
Regards,
JB
next prev parent reply other threads:[~2011-03-25 13:06 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 15:38 PCI passthrough issue Jean Baptiste Favre
2011-01-12 15:43 ` Konrad Rzeszutek Wilk
2011-01-12 15:53 ` Jean Baptiste Favre
2011-01-12 16:09 ` Jean Baptiste Favre
2011-01-12 16:36 ` Konrad Rzeszutek Wilk
2011-01-12 16:56 ` Jean Baptiste Favre
2011-01-12 17:26 ` Konrad Rzeszutek Wilk
2011-01-12 17:44 ` Jean Baptiste Favre
2011-01-12 18:32 ` Konrad Rzeszutek Wilk
2011-01-12 20:07 ` Jean Baptiste Favre
2011-01-12 21:40 ` Konrad Rzeszutek Wilk
2011-01-12 21:46 ` Jean Baptiste Favre
2011-01-12 22:18 ` Jean Baptiste Favre
2011-01-13 11:28 ` Jean Baptiste Favre
2011-01-13 19:18 ` Jean Baptiste Favre
2011-01-13 20:19 ` Konrad Rzeszutek Wilk
2011-01-13 20:44 ` Jean Baptiste Favre
2011-01-14 14:53 ` Konrad Rzeszutek Wilk
2011-01-14 23:29 ` Jean Baptiste Favre
2011-01-17 8:59 ` Jean Baptiste Favre
2011-01-17 13:58 ` Jean Baptiste Favre
2011-01-22 10:22 ` Jean Baptiste Favre
2011-01-27 20:27 ` Konrad Rzeszutek Wilk
2011-01-27 21:47 ` Jean Baptiste Favre
2011-01-28 15:47 ` Jean Baptiste Favre
2011-02-01 11:34 ` Ian Campbell
2011-02-01 12:17 ` Jean Baptiste Favre
2011-02-01 13:20 ` Ian Campbell
2011-02-01 14:12 ` Jean Baptiste Favre
2011-02-01 14:18 ` Ian Campbell
2011-02-01 15:14 ` Jean Baptiste Favre
2011-02-01 15:38 ` Jean Baptiste Favre
2011-02-01 16:23 ` Ian Campbell
2011-02-01 19:37 ` Konrad Rzeszutek Wilk
2011-02-01 22:06 ` Jean Baptiste Favre
2011-02-02 9:12 ` Ian Campbell
2011-02-01 23:01 ` Jean Baptiste Favre
2011-02-02 9:44 ` Ian Campbell
2011-02-02 15:38 ` Konrad Rzeszutek Wilk
2011-02-02 15:55 ` Ian Campbell
2011-02-02 15:56 ` Jean Baptiste Favre
2011-02-01 22:04 ` Jean Baptiste Favre
2011-02-02 9:27 ` Ian Campbell
2011-02-02 10:24 ` Jean Baptiste Favre
2011-02-02 10:59 ` Ian Campbell
2011-02-02 11:33 ` Jean Baptiste Favre
2011-02-02 17:42 ` Konrad Rzeszutek Wilk
2011-02-04 8:43 ` Jean Baptiste Favre
2011-02-04 8:53 ` Ian Campbell
2011-02-04 8:54 ` Jean Baptiste Favre
2011-02-04 10:12 ` Jean Baptiste Favre
2011-02-04 11:04 ` Ian Campbell
2011-02-04 11:25 ` Jean Baptiste Favre
2011-02-04 11:28 ` Ian Campbell
2011-02-04 13:15 ` Jean Baptiste Favre
2011-02-04 13:50 ` Ian Campbell
2011-02-04 14:01 ` Jean Baptiste Favre
2011-02-09 9:59 ` Jean Baptiste Favre
2011-02-18 21:14 ` Jean Baptiste Favre
2011-02-25 14:40 ` Konrad Rzeszutek Wilk
2011-02-28 10:00 ` Jean Baptiste Favre
2011-02-28 12:18 ` Jean Baptiste Favre
2011-02-28 15:01 ` Konrad Rzeszutek Wilk
2011-02-28 15:17 ` Jean Baptiste Favre
[not found] ` <4D6CB851.40103@jbfavre.org>
2011-03-03 22:12 ` Konrad Rzeszutek Wilk
2011-03-03 22:47 ` Jean Baptiste Favre
2011-03-03 22:58 ` Konrad Rzeszutek Wilk
2011-03-04 7:25 ` Jean Baptiste Favre
2011-03-16 3:14 ` Konrad Rzeszutek Wilk
2011-03-25 13:06 ` Jean Baptiste Favre [this message]
2011-02-01 15:38 ` Ian Campbell
2011-02-01 16:16 ` Jean Baptiste Favre
2011-01-12 21:44 ` Jean Baptiste Favre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D8C9343.4060801@jbfavre.org \
--to=xen-devel@jbfavre.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).