[lkml]   [2010]   [Jun]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Add a helper function in PCI IOV to get VF device
> So, when VF has no interface, this path is also unavailable. That's
> why I say given vf's bdf, one cannot infer pf's.

Sorry I just missed something. Userspace can find pf's bdf by physfn.

So, the motivation is provide some information about vf from pf driver by sysfs.

I cannot avoid to create one directory for each vf, like vf0, vf1,
etc. Although userspace can find these directories, but it has no idea
about which one to use. Userspace just knows vf's bdf, it won't care
about/know vf's id. So I have the issue to create a symlink from each
vf's /sys/bus/pci/devices/xxxx/ to their corresponding directories.

And then comes the issue: PF cannot get VF's bdf in kernel space.

This is not a strange issue, hacking every SR-IOV device can met.


Frank Pan

Computer Science and Technology
Tsinghua University

 \ /
  Last update: 2010-06-03 05:13    [W:0.837 / U:0.704 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site