| /openbmc/linux/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的数量。
48 在第二种方法中，对sysfs文件sriov_numvfs的写入将启用和禁用与PCIe PF相关的VF。
49 这种方法实现了每个PF的VF启用/禁用值，而第一种方法则适用于同一设备的所有PF。此外，
51 复，例如，如果启用VF，检查numvfs == 0，确保numvfs <= totalvfs。
52 第二种方法是对新的/未来的VF设备的推荐方法。
57 在内核中，VF被视为热插拔的PCI设备，所以它们应该能够以与真正的PCI设备相同的方式
58 工作。VF需要的设备驱动与普通PCI设备的驱动相同。
[all …]
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | pci_iov_resource_on_powernv.rst | 170 PCI devices, but the BARs in VF config space headers are unusual. For
171 a non-VF device, software uses BARs in the config space header to
172 discover the BAR sizes and assign addresses for them. For VF devices,
173 software uses VF BAR registers in the *PF* SR-IOV Capability to
174 discover sizes and assign addresses. The BARs in the VF's config space
177 When a VF BAR in the PF SR-IOV Capability is programmed, it sets the
178 base address for all the corresponding VF(n) BARs. For example, if the
180 1MB VF BAR0, the address in that VF BAR sets the base of an 8MB region.
182 is a BAR0 for one of the VFs. Note that even though the VF BAR
183 describes an 8MB region, the alignment requirement is for a single VF,
[all …]
|
| /openbmc/linux/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
88 virtio-net interface, and ens11 is the slave 'primary' VF passthrough interface.
93 and VF acquiring IP addresses (either same or different) from the DHCP server.
113 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode
117 with VMs that have direct attached SR-IOV VF devices by automatic failover to
118 the paravirtual datapath when the VF is unplugged.
122 software bridge 'br0' which has a single VF attached to it along with the vnet
[all …]
|
| H A D | representors.rst | 46 these administrative privileges instead to a VF or SF (subfunction).
56 the case of a VF representor, the representee is the corresponding VF.
81 on a VF representor applies in software to packets received on that representor
83 the representee VF. Conversely, a mirred egress redirect to a VF representor
84 corresponds in hardware to delivery directly to the representee VF.
111 PF or VF.
118 correspondence between VF netdevices and VF representors, more advanced device
196 ``REP_DEV`` is a VF representor, the following rules::
203 would mean that all IPv4 packets from the VF are sent out the physical port, and
204 all IPv4 packets received on the physical port are delivered to the VF in
[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.
|
| /openbmc/linux/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 Available for both PF and VF, and take no other effect on SEC.
111 Available for both PF and VF, and take no other effect on SEC.
[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 Available for both PF and VF, and take no other effect on HPRE.
131 Available for both PF and VF, and take no other effect on HPRE.
[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 Available for both PF and VF, and take no other effect on ZIP.
124 Available for both PF and VF, and take no other effect on ZIP.
[all …]
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | devlink-port.rst | 36 virtual function (VF).
142 The configured MAC address of the PCI VF/SF will be used by netdevice and rdma
143 device created for the PCI VF/SF.
145 - Get the MAC address of the VF identified by its unique devlink port index::
152 - Set the MAC address of the VF identified by its unique devlink port index::
181 When RoCE capability is disabled, it saves system memory per PCI VF/SF.
183 When user disables RoCE capability for a VF/SF, user application cannot send or
184 receive any RoCE packets through this VF/SF and RoCE GID table for this PCI
188 VF/SF driver cannot override it.
190 - Get RoCE capability of the VF device::
[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.
|
| /openbmc/linux/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
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | iavf.rst | 73 packets with VLAN tags, you can disable VLAN tag stripping for the VF. The
74 Physical Function (PF) processes requests issued from the VF to enable or
75 disable VLAN tag stripping. Note that if the PF has assigned a VLAN to a VF,
76 then requests from that VF to set VLAN tag stripping will be ignored.
78 To enable/disable VLAN tag stripping for a VF, issue the following command
79 from inside the VM in which you are running the VF::
89 Adaptive Virtual Function (AVF) allows the virtual function driver, or VF, to
106 - 1 Virtual Station Interface (VSI) per VF
110 - 1 unicast MAC address reserved per VF
111 - 16 MAC address filters for each VF
[all …]
|
| H A D | ice.rst | 20 The associated Virtual Function (VF) driver for this driver is iavf.
66 support SR-IOV, the virtual function (VF) may be subject to malicious behavior.
79 Do not unload port driver if VF with active VM is bound to it
81 Do not unload a port's driver if a Virtual Function (VF) with an active Virtual
83 Once the VM shuts down, or otherwise releases the VF, the command will
466 Use sysfs to enable virtual functions (VF).
485 Displaying VF Statistics on the PF
502 following command. The VLAN configuration should be done before the VF driver
503 is loaded or the VM is booted. The VF is not aware of the VLAN tag being
511 For example, the following will configure PF eth0 and the first VF on VLAN 10::
[all …]
|
| H A D | i40e.rst | 70 For example, the following instructions will configure PF eth0 and the first VF
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
87 Once the VF is designated as trusted, use the following commands in the VM to
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
101 "off",meaning that promiscuous mode for the VF will be limited. To set the
102 promiscuous mode for the VF to true promiscuous and allow the VF to see all
[all …]
|
| H A D | igb.rst | 80 ip link set eth0 vf 0 vlan 100 // set vlan 100 for VF 0
82 ip link set eth0 vf 0 vlan 200 // set a new vlan 200 for VF 0
170 Spoof event(s) detected on VF(n), where n = the VF that attempted to do the
176 You can set a MAC address of a Virtual Function (VF), a default VLAN and the
|
| /openbmc/qemu/docs/ |
| H A D | pcie_sriov.txt | 18 (PF) and the virtual device (VF). From QEMU's perspective, the VFs are just
28 <VF BAR start> + <VF number> * <BAR sz> + <offset>
31 setting up a BAR for a VF.
59 /* Set up individual VF BARs (parameters as for normal BARs) */
72 except for the SR/IOV capability. Then you need to set up the VF BARs as
73 subregions of the PFs SR/IOV VF BARs by calling
101 another VF count, and the emulation enforces this:
|
| /openbmc/linux/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
|
| /openbmc/linux/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
|
| /openbmc/linux/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
|
| /openbmc/linux/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
|
| /openbmc/linux/drivers/net/ethernet/freescale/enetc/ |
| H A D | Kconfig | 5 This module supports common functionality between the PF and VF
28 tristate "ENETC VF driver"
36 virtual function (VF) devices enabled by the ENETC PF driver.
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/marvell/ |
| H A D | octeontx2.rst | 28 PF/VF.
44 - A PF/VF with NIX-LF & NPA-LF resources works as a pure network device
45 - A PF/VF with CPT-LF resource works as a pure crypto offload device.
86 - Attach NIX and NPA block LFs to RVU PF/VF which provide buffer pools, RQs, SQs
123 the reply to VF.
124 - From functionality point of view there is no difference between PF and VF as same type
138 no other difference between these VF types. AF driver takes care of IO channel mapping,
139 hence same VF driver works for both types of devices.
|
| /openbmc/linux/drivers/media/platform/mediatek/mdp/ |
| H A D | mtk_mdp_regs.c | 14 #define MDP_COLORFMT_PACK(VIDEO, PLANE, COPLANE, HF, VF, BITS, GROUP, SWAP, ID)\ argument
16 ((HF) << 20) | ((VF) << 18) | ((BITS) << 8) | ((GROUP) << 6) |\
|
| /openbmc/linux/Documentation/fpga/ |
| H A D | dfl.rst | 384 | PF | | VF |
405 through virtual function (VF) devices via PCIe SRIOV. Each VF only contains
430 | PCI PF Device | | | PCI VF Device |
433 FPGA PCIe device driver is always loaded first once an FPGA PCIe PF or VF device
436 * Finishes enumeration on both FPGA PCIe PF and VF device using common
442 a port from PF, then it's safe to expose this port through a VF via PCIe SRIOV
446 respective AFU's port needs to be assigned to a VF using the following steps:
449 reassigned to a VF must first be released through the
453 to enable SRIOV and VFs. Each VF owns only one Port with AFU.
461 #. The AFU under VF is accessible from applications in VM (using the
[all …]
|