| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | debugfs-hisi-sec | 21 Available for PF and VF in host. VF in guest currently only
44 Available for both PF and VF, and take no other effect on SEC.
50 Available for both PF and VF, and take no other effect on SEC.
56 Available for both PF and VF, and take no other effect on SEC.
62 Available for both PF and VF, and take no other effect on SEC.
68 Available for both PF and VF, and take no other effect on SEC.
75 Available for both PF and VF, and take no other effect on SEC.
81 Available for both PF and VF, and take no other effect on SEC.
87 Available for both PF and VF, and take no other effect on SEC.
93 Available for both PF and VF, and take no other effect on SEC.
[all …]
|
| H A D | debugfs-hisi-hpre | 40 Available for PF and VF in host. VF in guest currently only
64 Available for both PF and VF, and take no other effect on HPRE.
70 Available for both PF and VF, and take no other effect on HPRE.
76 Available for both PF and VF, and take no other effect on HPRE.
82 Available for both PF and VF, and take no other effect on HPRE.
88 Available for both PF and VF, and take no other effect on HPRE.
95 Available for both PF and VF, and take no other effect on HPRE.
101 Available for both PF and VF, and take no other effect on HPRE.
107 Available for both PF and VF, and take no other effect on HPRE.
114 Available for both PF and VF, and take no other effect on HPRE.
[all …]
|
| H A D | debugfs-hisi-zip | 33 Available for PF and VF in host. VF in guest currently only
57 Available for both PF and VF, and take no other effect on ZIP.
63 Available for both PF and VF, and take no other effect on ZIP.
69 Available for both PF and VF, and take no other effect on ZIP.
75 Available for both PF and VF, and take no other effect on ZIP.
81 Available for both PF and VF, and take no other effect on ZIP.
88 Available for both PF and VF, and take no other effect on ZIP.
94 Available for both PF and VF, and take no other effect on ZIP.
100 Available for both PF and VF, and take no other effect on ZIP.
107 Available for both PF and VF, and take no other effect on ZIP.
[all …]
|
| H A D | debugfs-driver-genwqe | 70 Description: Default VF timeout 250ms. Testing might require 1000ms.
|
| /OK3568_Linux_fs/kernel/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 | 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
|
| H A D | ixgbe.rst | 225 ip link set eth0 vf 0 vlan 100 // set VLAN 100 for VF 0
227 ip link set eth0 vf 0 vlan 200 // set a new VLAN 200 for VF 0
242 Physical Function (PF) and each Virtual Function (VF) is allocated a pool of
250 each enabled VF is as follows:
399 bits represents the queue number, while the next 8 bits represent which VF.
400 Note that 0 is the PF, so the VF identifier is offset by 1. For example::
405 that VF.
440 a virtual function (VF), jumbo frames must first be enabled in the physical
441 function (PF). The VF MTU setting cannot be larger than the PF MTU.
517 NOTE: This feature can be disabled for a specific Virtual Function (VF)::
[all …]
|
| H A D | fm10k.rst | 52 ip link set eth0 vf 0 vlan 100 // set vlan 100 for VF 0
54 ip link set eth0 vf 0 vlan 200 // set a new vlan 200 for VF 0
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/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.
104 program on the associated VF NIC as well.
107 VF NIC automatically. Setting / unsetting XDP program on VF NIC directly
|
| /OK3568_Linux_fs/kernel/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.
76 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode
80 with VMs that have direct attached SR-IOV VF devices by automatic failover to
81 the paravirtual datapath when the VF is unplugged.
|
| 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.
|
| /OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/marvell/ |
| H A D | octeontx2.rst | 26 PF/VF.
42 - A PF/VF with NIX-LF & NPA-LF resources works as a pure network device
43 - A PF/VF with CPT-LF resource works as a pure crypto offload device.
84 - Attach NIX and NPA block LFs to RVU PF/VF which provide buffer pools, RQs, SQs
121 the reply to VF.
122 - From functionality point of view there is no difference between PF and VF as same type
136 no other difference between these VF types. AF driver takes care of IO channel mapping,
137 hence same VF driver works for both types of devices.
|
| /OK3568_Linux_fs/kernel/Documentation/fpga/ |
| H A D | dfl.rst | 264 | PF | | VF |
285 through virtual function (VF) devices via PCIe SRIOV. Each VF only contains
310 | PCI PF Device | | | PCI VF Device |
313 FPGA PCIe device driver is always loaded first once a FPGA PCIe PF or VF device
316 * Finishes enumeration on both FPGA PCIe PF and VF device using common
322 a port from PF, then it's safe to expose this port through a VF via PCIe SRIOV
326 respective AFU's port needs to be assigned to a VF using the following steps:
329 reassigned to a VF must first be released through the
333 to enable SRIOV and VFs. Each VF owns only one Port with AFU.
341 #. The AFU under VF is accessible from applications in VM (using the
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/vdpa/ |
| H A D | Kconfig | 24 tristate "Intel IFC VF vDPA driver"
28 This kernel module can drive Intel IFC VF NIC to offload
|
| /OK3568_Linux_fs/kernel/drivers/net/ethernet/freescale/enetc/ |
| H A D | Kconfig | 17 tristate "ENETC VF driver"
24 virtual function (VF) devices enabled by the ENETC PF driver.
|
| /OK3568_Linux_fs/kernel/drivers/media/platform/mtk-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) |\
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/media/xilinx/ |
| H A D | video.txt | 21 AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
|
| /OK3568_Linux_fs/kernel/tools/build/ |
| H A D | Makefile.feature | 234 ifeq ($(VF),1)
|
| /OK3568_Linux_fs/kernel/drivers/net/ethernet/cavium/ |
| H A D | Kconfig | 92 tristate "Cavium LiquidIO VF support"
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/stable/ |
| H A D | sysfs-class-infiniband | 387 Enabling QP0 on VFs for selected VF/port. By default, no VFs are
392 for the indicated VF/port
396 indicated VF/port. 0 = disable, 1 = enable.
399 The requested enablement will occur at the next reset of the VF
400 (e.g. driver restart on the VM which owns the VF).
|
| /OK3568_Linux_fs/kernel/drivers/net/ethernet/hisilicon/ |
| H A D | Kconfig | 124 This selects the HNS3 VF drivers network acceleration engine & its hardware
|
| /OK3568_Linux_fs/kernel/Documentation/scsi/ |
| H A D | scsi_fc_transport.rst | 49 (just like a normal non-NPIV adapter). Using the Virtual Fabric (VF)
54 used together with VF so that the port can obtain multiple N_Port_IDs
73 vports. However, consideration was given to VF-based vports and it
|