Home
last modified time | relevance | path

Searched refs:VF (Results 1 – 25 of 40) sorted by relevance

12

/linux/Documentation/powerpc/
A Dpci_iov_resource_on_powernv.rst180 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/Documentation/ABI/testing/
A Ddebugfs-hisi-sec21 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 …]
A Ddebugfs-hisi-hpre40 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 …]
A Ddebugfs-hisi-zip33 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 …]
/linux/Documentation/networking/device_drivers/ethernet/intel/
A Diavf.rst74 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 …]
A Dice.rst503 Displaying VF Statistics on the PF
546 Setting the MAC Address for a VF
564 Trusted VFs and VF Promiscuous Mode
576 VF. If the VM becomes trusted after the VF driver is loaded, you must make a
577 new request to set the VF to promiscuous.
580 set the VF to promiscuous mode.
585 Where <ethX> is a VF interface in the VM
594 promiscuous mode for the VF to true promiscuous and allow the VF to see all
623 - If the PF driver logs MDD events from the VF, confirm that the correct VF
626 automatic VF resets.
[all …]
A Di40e.rst78 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
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
115 Now add a VLAN interface on the VF interface::
286 that VF.
[all …]
A Digb.rst80 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
A Dixgbe.rst225 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 …]
A Dfm10k.rst52 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
/linux/Documentation/PCI/
A Dpci-iov-howto.rst21 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/Documentation/networking/device_drivers/ethernet/microsoft/
A Dnetvsc.rst71 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/Documentation/networking/devlink/
A Docteontx2.rst7 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.
A Dnetdevsim.rst65 - registerging/unregistering leaf rate objects per VF devlink port;
/linux/Documentation/networking/
A Dnet_failover.rst25 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.
A Dfailover.rst16 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/Documentation/networking/device_drivers/ethernet/marvell/
A Docteontx2.rst27 PF/VF.
43 - A PF/VF with NIX-LF & NPA-LF resources works as a pure network device
44 - A PF/VF with CPT-LF resource works as a pure crypto offload device.
85 - Attach NIX and NPA block LFs to RVU PF/VF which provide buffer pools, RQs, SQs
122 the reply to VF.
123 - From functionality point of view there is no difference between PF and VF as same type
137 no other difference between these VF types. AF driver takes care of IO channel mapping,
138 hence same VF driver works for both types of devices.
/linux/Documentation/fpga/
A Ddfl.rst265 | PF | | VF |
286 through virtual function (VF) devices via PCIe SRIOV. Each VF only contains
311 | PCI PF Device | | | PCI VF Device |
317 * Finishes enumeration on both FPGA PCIe PF and VF device using common
323 a port from PF, then it's safe to expose this port through a VF via PCIe SRIOV
327 respective AFU's port needs to be assigned to a VF using the following steps:
330 reassigned to a VF must first be released through the
334 to enable SRIOV and VFs. Each VF owns only one Port with AFU.
342 #. The AFU under VF is accessible from applications in VM (using the
343 same driver inside the VF).
[all …]
/linux/drivers/net/ethernet/freescale/enetc/
A DKconfig18 tristate "ENETC VF driver"
25 virtual function (VF) devices enabled by the ENETC PF driver.
/linux/drivers/media/platform/mtk-mdp/
A Dmtk_mdp_regs.c14 #define MDP_COLORFMT_PACK(VIDEO, PLANE, COPLANE, HF, VF, BITS, GROUP, SWAP, ID)\ argument
16 ((HF) << 20) | ((VF) << 18) | ((BITS) << 8) | ((GROUP) << 6) |\
/linux/drivers/vdpa/
A DKconfig47 tristate "Intel IFC VF vDPA driver"
50 This kernel module can drive Intel IFC VF NIC to offload
/linux/Documentation/networking/device_drivers/ethernet/mellanox/
A Dmlx5.rst199 2. VF/SF representor bonding (Usually used for Live migration)
343 The mlx5 driver provides a mechanism to setup PCI VF/SF function attributes in
347 configuration of the PCI VF/SF is supported through devlink eswitch port.
349 Port function attributes should be set before PCI VF/SF is enumerated by the
354 mlx5 driver provides mechanism to setup the MAC address of the PCI VF/SF.
356 The configured MAC address of the PCI VF/SF will be used by netdevice and rdma
357 device created for the PCI VF/SF.
359 - Get the MAC address of the VF identified by its unique devlink port index::
366 - Set the MAC address of the VF identified by its unique devlink port index::
382 - Set the MAC address of the VF identified by its unique devlink port index::
[all …]
/linux/drivers/net/ethernet/mellanox/mlx5/core/
A DKconfig86 Enable adding representors of mlx5 uplink and VF ports to Bridge and
225 It is similar to a SRIOV VF but it doesn't require SRIOV support.
234 and vdpa device. It is similar to a SRIOV VF but it doesn't require
/linux/Documentation/devicetree/bindings/media/xilinx/
A Dvideo.txt21 AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
/linux/tools/build/
A DMakefile.feature237 ifeq ($(VF),1)

Completed in 40 milliseconds

12