WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 24 Aug 2007 16:01:48 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Sanjeev Jorapur <sanjeev@xxxxxxxxxx>
Delivery-date: Fri, 24 Aug 2007 08:02:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46CEF208.4090108@xxxxxxxxxx>
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: AcfmX7Gk7/85rVJSEdyesQAX8io7RQ==
Thread-topic: [Xen-devel] PCI Passthru: fn0 exported but not fn1
User-agent: Microsoft-Entourage/11.3.6.070618
Why did you not use VPCI? Does that not work for you? It should avoid the
problem that is currently blocking your progress.

 -- Keir


On 24/8/07 15:58, "Jambunathan K" <jambunathan@xxxxxxxxxx> wrote:

> CONFIG_XEN_PCIDEV_FRONTEND=y
> CONFIG_XEN_PCIDEV_FE_DEBUG=y
> CONFIG_XEN_PCIDEV_BACKEND=y
> # CONFIG_XEN_PCIDEV_BACKEND_VPCI is not set
> CONFIG_XEN_PCIDEV_BACKEND_PASS=y
> # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
> CONFIG_XEN_PCIDEV_BE_DEBUG=y
> 
> I have overridden default VPCI with explicit BACKEND_PASS. Both Dom0 and
> Dom1 run the same kernel binary.
> 
> I had used the above configuration all along (on both Xen304 + Xen310)
> and have seen fn1 exported 'as such' to Dom1. It is with my new box that
> I have the above issue.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel