Re: [Xen-devel] PCI Passthru: fn0 exported but not fn1

[Jambunathan K <jambunathan@xxxxxxxxxx>]

>> I think it's not usual to scan non-zero fns of a PCI slot if fn0 is empty.
>> But actually pciback should be renaming the devfn address to a fn0 address
>> anyway, unless you fiddled with pciback's kernel configuration. If you grep
>> for PCIDEV_BACKEND in your kernel build configuration, what do you see?
>> 
>>  -- Keir
>> 
>> On 23/8/07 20:04, "Jambunathan K" <jambunathan@xxxxxxxxxx> wrote:
>> 
>>> Given the following device list,  I am exporting one of the functions to
>>> Dom1 through PCI passthrough.
>>>
>>> $ lspci | grep known
>>> 04:00.0 Ethernet controller: Unknown device 4040:0002 (rev 25)
>>> 04:00.1 Ethernet controller: Unknown device 4040:0002 (rev 25)
>>> 04:00.2 Ethernet controller: Unknown device 4040:0002 (rev 25)
>>> 04:00.3 Ethernet controller: Unknown device 4040:0002 (rev 25)
>>>
>>> If I export just 04:00.0,  it is visible ('lspci') in Dom1. However if I
>>> export just 04:00.1 then it is no more visible in Dom1.
>>>


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.

Jambunathan K.


Keir Fraser wrote:
> I think it's not usual to scan non-zero fns of a PCI slot if fn0 is empty.
> But actually pciback should be renaming the devfn address to a fn0 address
> anyway, unless you fiddled with pciback's kernel configuration. If you grep
> for PCIDEV_BACKEND in your kernel build configuration, what do you see?
> 
>  -- Keir
> 
> On 23/8/07 20:04, "Jambunathan K" <jambunathan@xxxxxxxxxx> wrote:
> 
>> Given the following device list,  I am exporting one of the functions to
>> Dom1 through PCI passthrough.
>>
>> $ lspci | grep known
>> 04:00.0 Ethernet controller: Unknown device 4040:0002 (rev 25)
>> 04:00.1 Ethernet controller: Unknown device 4040:0002 (rev 25)
>> 04:00.2 Ethernet controller: Unknown device 4040:0002 (rev 25)
>> 04:00.3 Ethernet controller: Unknown device 4040:0002 (rev 25)
>>
>> If I export just 04:00.0,  it is visible ('lspci') in Dom1. However if I
>> export just 04:00.1 then it is no more visible in Dom1.
>>
>> I am using Xen310. As an additional information, I am seeing this
>> behaviour on my 'new box'. Things were fine on my earlier box. It is
>> possible that this is a platform specific thing.
>>
>> If it is a known issue, I would be happy to patch my tree. Otherwise I
>> can debug this further post some debug logs for your scrutiny.
>>
>> Jambunathan K.
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 


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