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 Passthru: fn0 exported but not fn1

To: Jambunathan K <jambunathan@xxxxxxxxxx>
Subject: Re: [Xen-devel] PCI Passthru: fn0 exported but not fn1
From: Stefan Neuwirth <neuwirt-xen-devel@xxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 29 Aug 2007 20:27:25 +0200
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>, Sanjeev Jorapur <sanjeev@xxxxxxxxxx>
Delivery-date: Wed, 29 Aug 2007 14:10:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46D58037.7010007@xxxxxxxxxx> (Jambunathan K.'s message of "Wed, 29 Aug 2007 19:48:31 +0530")
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C2FA6F3A.D05F%keir@xxxxxxxxxxxxx> <46D58037.7010007@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux)
Jambunathan K <jambunathan@xxxxxxxxxx> 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.


Xen-devel mailing list