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: Stefan Neuwirth <neuwirt-xen-devel@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] PCI Passthru: fn0 exported but not fn1
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Wed, 29 Aug 2007 00:32:58 +0100
Cc: Jambunathan K <jambunathan@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Sanjeev Jorapur <sanjeev@xxxxxxxxxx>
Delivery-date: Tue, 28 Aug 2007 16:29:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <87tzqje7yf.fsf@xxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acfpy8QKArBPilW/EdyjPAAWy6hiGQ==
Thread-topic: [Xen-devel] PCI Passthru: fn0 exported but not fn1
User-agent: Microsoft-Entourage/
> 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!

Let me know how you get on -- if successful I may check this change back
into our linux-2.6.18-xen.hg repository.

 -- Keir

Xen-devel mailing list