>-----Original Message----- >From: Greg KH [mailto:greg@xxxxxxxxx] >Sent: Tuesday, June 01, 2010 11:39 AM > >On Tue, Jun 01, 2010 at 01:05:25PM +0800, Frank Pan wrote: >> Greetings, >> >> The motivation is make VF device visible to PF driver. PF driver >> may need this to access VF's PCI configuration. > >What is "VF" and "PF" here? > >> Another use case is in sysfs symbolic linking. Some of VF's sysfs >> entries are created by PF driver. For example, /sys/class/net/ethx/vfx >> in Intel 82576 NIC driver. Makeing a symbolic link from VF's pci device >> to this path also must be done in PF's driver. > >No, the network core should create that symlink, not the driver, right? > >thanks, > >greg k-h Furthermore, the links are already there in sysfs, created by the PCI subsystem. /sys/class/net/ethX/device links to the PCI device entry for the PF device, which itself has symlinks to each of the VF devices. This patch just isn't necessary. -Mitch -- 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
