>-----Original Message----- >From: Frank Pan [mailto:frankpzh@xxxxxxxxx] >Sent: Wednesday, June 02, 2010 8:11 PM [snip] >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, I still don't understand what you're trying to do here. What's the use case? What is the end goal that you're trying to get to? What information do you need about the VF, and why? SR-IOV works properly today without this stuff. If we can understand what you're trying to do, then maybe we can help. -Mitch >Thanks. > >-- >Frank Pan > >Computer Science and Technology >Tsinghua University -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
