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: Mon, 27 Aug 2007 16:40:51 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Sanjeev Jorapur <sanjeev@xxxxxxxxxx>
Delivery-date: Mon, 27 Aug 2007 08:37:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46D2ED75.1000906@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: AcfowKVr49t7/lSzEdy1YgAWy6hiGQ==
Thread-topic: [Xen-devel] PCI Passthru: fn0 exported but not fn1
User-agent: Microsoft-Entourage/11.3.3.061214
On 27/8/07 16:27, "Jambunathan K" <jambunathan@xxxxxxxxxx> wrote:

>>> For now I have reverted my working tree to Xen-304. I would appreciate
>>> if you could provide a patch that addresses this issue in Xen310.
>> 
>> What is the regression? That pcifront does not scan fn!=0 if fn==0 is empty?
>> 
>>  -- Keir
>> 
> 
> Behaviorally speaking, I can export *just* fn1 on Xen304. But I can't
> export *just* fn1 on Xen310.
> 
> I am calling this difference in behaviour a regression.

You mean pciback doesn't let you, or do you mean it lets you but then
pcifront doesn't pick it up because it has fn!=0? And if you force it to be
renamed to have fn==0 then some assumption in your device driver is broken?
I think you're a long way down a diagnosis path that I haven't followed...

 -- Keir



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