summaryrefslogtreecommitdiffstats
path: root/drivers/net/hyperv/netvsc_drv.c
diff options
context:
space:
mode:
authorStephen Hemminger2018-09-14 21:54:56 +0200
committerDavid S. Miller2018-09-17 16:59:41 +0200
commita15f2c08c70811f120d99288d81f70d7f3d104f1 (patch)
tree11c90439f7fa23e52d1a4ac07472f361439f344e /drivers/net/hyperv/netvsc_drv.c
parentbnxt_en: Fix VF mac address regression. (diff)
downloadkernel-qcow2-linux-a15f2c08c70811f120d99288d81f70d7f3d104f1.tar.gz
kernel-qcow2-linux-a15f2c08c70811f120d99288d81f70d7f3d104f1.tar.xz
kernel-qcow2-linux-a15f2c08c70811f120d99288d81f70d7f3d104f1.zip
PCI: hv: support reporting serial number as slot information
The Hyper-V host API for PCI provides a unique "serial number" which can be used as basis for sysfs PCI slot table. This can be useful for cases where userspace wants to find the PCI device based on serial number. When an SR-IOV NIC is added, the host sends an attach message with serial number. The kernel doesn't use the serial number, but it is useful when doing the same thing in a userspace driver such as the DPDK. By having /sys/bus/pci/slots/N it provides a direct way to find the matching PCI device. There maybe some cases where serial number is not unique such as when using GPU's. But the PCI slot infrastructure will handle that. This has a side effect which may also be useful. The common udev network device naming policy uses the slot information (rather than PCI address). Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/hyperv/netvsc_drv.c')
0 files changed, 0 insertions, 0 deletions