| /linux-6.15/Documentation/translations/zh_CN/PCI/ |
| H A D | pci-iov-howto.rst | 32 虚拟设备。物理设备被称为物理功能（PF），而虚拟设备被称为虚拟功能（VF）。VF的分
34 现为传统的PCIe设备。一旦开启，每个VF的PCI配置空间都可以通过自己的总线、设备和
35 功能编号（路由ID）来访问。而且每个VF也有PCI内存空间，用于映射其寄存器集。VF设
47 用它和与PF相关的所有VF。一些PF驱动需要设置一个模块参数，以确定要启用的VF的数量。
49 这种方法实现了每个PF的VF启用/禁用值，而第一种方法则适用于同一设备的所有PF。此外，
52 第二种方法是对新的/未来的VF设备的推荐方法。
57 在内核中，VF被视为热插拔的PCI设备，所以它们应该能够以与真正的PCI设备相同的方式
58 工作。VF需要的设备驱动与普通PCI设备的驱动相同。
72 nr_virtfn'是要启用的VF的编号。
90 要想通过主机上的兼容驱动启用自动探测VF，在启用SR-IOV功能之前运行下面的命令。这
[all …]
|
| /linux-6.15/Documentation/arch/powerpc/ |
| H A D | pci_iov_resource_on_powernv.rst | 180 1MB VF BAR0, the address in that VF BAR sets the base of an 8MB region.
195 the segment size matches the smallest VF BAR, which means larger VF
227 SR-IOV VF BARs are all the same size.
244 VF(n) BAR space
253 Figure 1.0 Direct map VF(n) BAR space
272 Figure 1.1 Map VF(n) BAR space + extra
285 aligned to the size of an individual VF BAR.
294 of the VF(n) BAR space in the VF BAR. If the PCI core allocates the exact
295 amount of space required for the VF(n) BAR space, the VF BAR value is fixed
303 Then each VF will be in its own PE. The VF BARs (and therefore the PE#s)
[all …]
|
| /linux-6.15/Documentation/networking/ |
| H A D | net_failover.rst | 25 direct attached VF by failing over to the paravirtual datapath when the VF
36 virtio-net and VF interfaces.
64 the VF passthrough device for normal communication. The virtio-net device will
67 The second device definition is for the VF passthrough interface. Here the
113 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode
118 the paravirtual datapath when the VF is unplugged.
141 VF=ens6v1 # VF attached to the bridge.
152 # Remove the VF that was passthrough'd to the VM.
158 # the VF -> br0 -> vnet interface path.
159 bridge fdb add $MAC dev $VF
[all …]
|
| H A D | representors.rst | 47 these administrative privileges instead to a VF or SF (subfunction).
57 the case of a VF representor, the representee is the corresponding VF.
82 on a VF representor applies in software to packets received on that representor
84 the representee VF. Conversely, a mirred egress redirect to a VF representor
85 corresponds in hardware to delivery directly to the representee VF.
112 PF or VF.
119 correspondence between VF netdevices and VF representors, more advanced device
197 ``REP_DEV`` is a VF representor, the following rules::
205 all IPv4 packets received on the physical port are delivered to the VF in
207 the VF would get two copies, as the packet reception on ``PORT_DEV`` would
[all …]
|
| H A D | failover.rst | 16 This enables paravirtual drivers to use a VF as an accelerated low latency
18 failing over to the paravirtual datapath when the VF is unplugged.
|
| /linux-6.15/Documentation/misc-devices/ |
| H A D | mrvl_cn10k_dpi.rst | 15 requests from its VF functions and provisions DMA engine resources to
16 it's VF functions.
19 mailbox commands submitted by the VF devices and accordingly initializes
20 the DMA engines and VF device's DMA command queues. Also, driver creates
24 DPI PF driver is just an administrative driver to setup its VF device's
26 DMA operations. Only VF devices are provisioned with DMA capabilities.
48 DPI VF devices are probed and accessed from user space applications using
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A D | debugfs-hisi-sec | 20 Description: The <bdf> is related the function for PF and VF.
31 Available for PF and VF in host. VF in guest currently only
54 Available for both PF and VF, and take no other effect on SEC.
60 Available for both PF and VF, and take no other effect on SEC.
66 Available for both PF and VF, and take no other effect on SEC.
72 Available for both PF and VF, and take no other effect on SEC.
78 Available for both PF and VF, and take no other effect on SEC.
85 Available for both PF and VF, and take no other effect on SEC.
105 and VF, and take no other effect on SEC.
113 will return non-zero value. Available for both PF and VF,
[all …]
|
| H A D | debugfs-hisi-hpre | 33 Description: The <bdf> is related the function for PF and VF.
50 Available for PF and VF in host. VF in guest currently only
74 Available for both PF and VF, and take no other effect on HPRE.
80 Available for both PF and VF, and take no other effect on HPRE.
86 Available for both PF and VF, and take no other effect on HPRE.
92 Available for both PF and VF, and take no other effect on HPRE.
98 Available for both PF and VF, and take no other effect on HPRE.
105 Available for both PF and VF, and take no other effect on HPRE.
125 and VF, and take no other effect on HPRE.
133 will return non-zero value. Available for both PF and VF,
[all …]
|
| H A D | debugfs-hisi-zip | 32 Description: The <bdf> is related the function for PF and VF.
43 Available for PF and VF in host. VF in guest currently only
67 Available for both PF and VF, and take no other effect on ZIP.
73 Available for both PF and VF, and take no other effect on ZIP.
79 Available for both PF and VF, and take no other effect on ZIP.
85 Available for both PF and VF, and take no other effect on ZIP.
91 Available for both PF and VF, and take no other effect on ZIP.
98 Available for both PF and VF, and take no other effect on ZIP.
118 and VF, and take no other effect on ZIP.
126 will return non-zero value. Available for both PF and VF,
[all …]
|
| H A D | debugfs-driver-qat_telemetry | 165 If Virtual Functions (VF) are used, the ring pair number can
166 be derived from the Bus, Device, Function of the VF:
169 PCI BDF/VF RP0 RP1 RP2 RP3
201 PCI BDF/VF RP0/service RP1/service RP2/service RP3/service
216 PCI BDF/VF RP0/service RP1/service RP2/service RP3/service
|
| /linux-6.15/Documentation/networking/device_drivers/ethernet/amd/ |
| H A D | pds_vfio_pci.rst | 15 capable Virtual Function (VF) devices in the DSC hardware.
24 Shown below are the steps to bind the driver to a VF and also to the
38 # Prevent non-vfio VF driver from probing the VF device
41 # Create single VF for Live Migration via pds_core
44 # Allow the VF to be bound to the pds-vfio-pci driver
47 # Bind the VF to the pds-vfio-pci driver
|
| H A D | pds_vdpa.rst | 8 AMD/Pensando vDPA VF Device Driver
19 and VF PCI handling as well as for device configuration services.
41 # Enable vDPA VF auxiliary device(s) in the PF
44 # Create a VF for vDPA use
|
| /linux-6.15/Documentation/networking/devlink/ |
| H A D | devlink-port.rst | 36 virtual function (VF).
146 device created for the PCI VF/SF.
191 VF/SF driver cannot override it.
193 - Get RoCE capability of the VF device::
200 - Set RoCE capability of the VF device::
216 explicitly enable the VF migratable capability.
218 When user enables migratable capability for a VF, and the HV binds the VF to VFIO driver
226 - Get migratable capability of the VF device::
233 - Set migratable capability of the VF device::
248 Attach VF to the VM.
[all …]
|
| H A D | octeontx2.rst | 7 This document describes the devlink features implemented by the ``octeontx2 AF, PF and VF``
13 The ``octeontx2 PF and VF`` drivers implement the following driver-specific parameters.
27 PF and VF drivers.
54 The default rule serves as the primary packet steering rule for a specific PF or VF,
|
| /linux-6.15/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | iavf.rst | 74 Physical Function (PF) processes requests issued from the VF to enable or
76 then requests from that VF to set VLAN tag stripping will be ignored.
79 from inside the VM in which you are running the VF::
106 - 1 Virtual Station Interface (VSI) per VF
110 - 1 unicast MAC address reserved per VF
111 - 16 MAC address filters for each VF
114 - HW mailbox is used for VF to PF communications (including on Windows)
232 if the VF's MAC address is not set by the PF.
245 Do not unload port driver if VF with active VM is bound to it
263 Unable to send the message to VF 2 aq_err 12
[all …]
|
| H A D | ice.rst | 529 Displaying VF Statistics on the PF
572 Setting the MAC Address for a VF
590 Trusted VFs and VF Promiscuous Mode
602 VF. If the VM becomes trusted after the VF driver is loaded, you must make a
603 new request to set the VF to promiscuous.
606 set the VF to promiscuous mode.
611 Where <ethX> is a VF interface in the VM
620 promiscuous mode for the VF to true promiscuous and allow the VF to see all
649 - If the PF driver logs MDD events from the VF, confirm that the correct VF
652 automatic VF resets.
[all …]
|
| H A D | i40e.rst | 78 virtual function (VF). Further, this feature allows you to designate a
79 particular VF as trusted, and allows that trusted VF to request selective
82 To set a VF as trusted or untrusted, enter the following command in the
88 set the VF to promiscuous mode.
94 Where eth2 is a VF interface in the VM
98 Where eth2 is a VF interface in the VM
102 promiscuous mode for the VF to true promiscuous and allow the VF to see all
115 Now add a VLAN interface on the VF interface::
286 that VF.
307 set to "off", the problematic VF will be disabled.
[all …]
|
| /linux-6.15/Documentation/PCI/ |
| H A D | pci-iov-howto.rst | 21 while the virtual devices are referred to as Virtual Functions (VF).
22 Allocation of the VF can be dynamically controlled by the PF via
25 turned on, each VF's PCI configuration space can be accessed by its own
26 Bus, Device and Function Number (Routing ID). And each VF also has PCI
27 Memory Space, which is used to map its register set. VF device driver
45 enables per-PF, VF enable/disable values versus the first method,
51 The second method is the recommended method for new/future VF devices.
56 The VF is treated as hot-plugged PCI devices in the kernel, so they
57 should be able to work in the same way as real PCI devices. The VF
|
| /linux-6.15/drivers/vfio/pci/virtio/ |
| H A D | Kconfig | 3 tristate "VFIO support for VIRTIO PCI VF devices"
7 This provides migration support for VIRTIO NET and BLOCK PCI VF
20 bool "Legacy I/O support for VIRTIO NET PCI VF devices"
26 PCI VF devices. Legacy I/O support requires the SR-IOV PF
|
| /linux-6.15/drivers/net/ethernet/marvell/octeon_ep_vf/ |
| H A D | Kconfig | 3 # Marvell's Octeon PCI Endpoint NIC VF Driver Configuration
7 tristate "Marvell Octeon PCI Endpoint NIC VF Driver"
12 Octeon PCI Endpoint NIC VF.
|
| /linux-6.15/Documentation/networking/device_drivers/ethernet/marvell/ |
| H A D | octeon_ep_vf.rst | 4 Linux kernel networking driver for Marvell's Octeon PCI Endpoint NIC VF
7 Network driver for Marvell's Octeon PCI EndPoint NIC VF.
13 EndPoint NIC VF.
|
| /linux-6.15/Documentation/networking/device_drivers/ethernet/microsoft/ |
| H A D | netvsc.rst | 71 Virtual Function (VF) device is passed to the guest as a PCI
72 device. In this case, both a synthetic (netvsc) and VF device are
75 The VF is enslaved by netvsc device. The netvsc driver will transparently
76 switch the data path to the VF when it is available and up.
81 VF slave device.
108 program on the associated VF NIC as well.
111 VF NIC automatically. Setting / unsetting XDP program on VF NIC directly
|
| /linux-6.15/Documentation/admin-guide/perf/ |
| H A D | hns3-pmu.rst | 106 PMU collect performance statistic of one PF/VF. The function id is BDF of
107 PF/VF, its conversion formula::
123 PMU collect performance statistic of one queue of PF/VF. The function id
124 is BDF of PF/VF, the "queue" filter option must be set to the exact queue
131 PMU collect performance statistic of one interrupt of PF/VF. The function
132 id is BDF of PF/VF, the "intr" filter option must be set to the exact
|
| /linux-6.15/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| H A D | switchdev.rst | 160 The mlx5 driver provides a mechanism to setup PCI VF/SF function attributes in
164 configuration of the PCI VF/SF is supported through devlink eswitch port.
166 Port function attributes should be set before PCI VF/SF is enumerated by the
188 explicitly enable the VF migratable capability.
196 to explicitly enable the VF ipsec_crypto capability. Enabling IPsec capability
197 for VFs is supported starting with ConnectX6dx devices and above. When a VF has
206 to explicitly enable the VF ipsec_packet capability. Enabling IPsec capability
207 for VFs is supported starting with ConnectX6dx devices and above. When a VF has
|
| /linux-6.15/drivers/net/ethernet/freescale/enetc/ |
| H A D | Kconfig | 5 This module supports common functionality between the PF and VF
54 tristate "ENETC VF driver"
62 virtual function (VF) devices enabled by the ENETC PF driver.
|