From: Stefan Neuwirth <neuwirt-xen-devel@trillian.hd.shuttle.de>
To: Jambunathan K <jambunathan@netxen.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xensource.com>,
Sanjeev Jorapur <sanjeev@netxen.com>
Subject: Re: PCI Passthru: fn0 exported but not fn1
Date: Wed, 29 Aug 2007 20:27:25 +0200 [thread overview]
Message-ID: <87ejhm5h82.fsf@trillian.hd.shuttle.de> (raw)
In-Reply-To: <46D58037.7010007@netxen.com> (Jambunathan K.'s message of "Wed, 29 Aug 2007 19:48:31 +0530")
Jambunathan K <jambunathan@netxen.com> writes:
> Keir Fraser wrote:
>>> As I worte accidently direct to Keir and not to the list, I face the
>>> same problem. I'd like to have option 1, because it worked fine and I
>>> don't see a benefit of having a dummy device in the domU.
>>>
>>> Dedecating single fnX to a domain is very usefull for example to give
>>> the domUs ethernets of a four port card. I'm also running one domU
>>> that is only using one of the USB 1.x controllers of a USB PCI addon
>>> card.
>>
>> Okay, if you want to check out the 'fix' to revert behaviour to that of
>> 3.0.4 for yourselves, it is to edit
>> linux/include/asm-i386/mach-xen/asm/pci.h and to change the definition
>> therein of pcibios_scan_all_fns() from 0 to 1.
>>
>> If you are building a 64-bit kernel then of course it is the file in
>> include/asm-x86_64 that you need to edit.
>>
>> Make that change and rebuild you domU. Additionally, make sure you build
>> dom0 with pciback in passthrough mode. Hopefully your problems will be gone!
>
>
> I am using x86_64.
Same here.
> Just to be sure I 'fixed'
> linux-2.6-xen-sparse/include/asm-x86_64/mach-xen/asm/pci.h and made a
> clean build from xen source tar. I ensured that BACKEND_PASS is set to yes.
>
> I am using the same vmlinuz both on Dom0 and Dom1. I am seeing that
> lspci in Dom1 *doesn't* report the exported non-zero function.
Same here, furthermore the system was unresponsive to my serial device
with the fix applied.
Stefan
next prev parent reply other threads:[~2007-08-29 18:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C2FA6F3A.D05F%keir@xensource.com>
2007-08-29 14:18 ` PCI Passthru: fn0 exported but not fn1 Jambunathan K
2007-08-29 14:26 ` Keir Fraser
2007-08-30 10:11 ` Jambunathan K
2007-08-30 10:19 ` Keir Fraser
2007-08-30 14:45 ` Jambunathan K
2007-08-29 18:27 ` Stefan Neuwirth [this message]
2007-08-23 19:04 Jambunathan K
2007-08-24 14:42 ` Keir Fraser
2007-08-24 14:58 ` Jambunathan K
2007-08-24 15:01 ` Keir Fraser
2007-08-26 16:19 ` Jambunathan K
2007-08-27 14:08 ` Jambunathan K
2007-08-27 15:22 ` Keir Fraser
2007-08-27 15:27 ` Jambunathan K
2007-08-27 15:40 ` Keir Fraser
2007-08-27 15:58 ` Jambunathan K
2007-08-27 16:14 ` Keir Fraser
2007-08-27 16:34 ` Jambunathan K
2007-08-27 16:42 ` Keir Fraser
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=87ejhm5h82.fsf@trillian.hd.shuttle.de \
--to=neuwirt-xen-devel@trillian.hd.shuttle.de \
--cc=jambunathan@netxen.com \
--cc=keir@xensource.com \
--cc=sanjeev@netxen.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.