Home
last modified time | relevance | path

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

/Linux-v4.19/Documentation/powerpc/
Dpci_iov_resource_on_powernv.txt160 PCI devices, but the BARs in VF config space headers are unusual. For
161 a non-VF device, software uses BARs in the config space header to
162 discover the BAR sizes and assign addresses for them. For VF devices,
163 software uses VF BAR registers in the *PF* SR-IOV Capability to
164 discover sizes and assign addresses. The BARs in the VF's config space
167 When a VF BAR in the PF SR-IOV Capability is programmed, it sets the
168 base address for all the corresponding VF(n) BARs. For example, if the
170 1MB VF BAR0, the address in that VF BAR sets the base of an 8MB region.
172 is a BAR0 for one of the VFs. Note that even though the VF BAR
173 describes an 8MB region, the alignment requirement is for a single VF,
[all …]
/Linux-v4.19/Documentation/PCI/
Dpci-iov-howto.txt16 while the virtual devices are referred to as Virtual Functions (VF).
17 Allocation of the VF can be dynamically controlled by the PF via
20 turned on, each VF's PCI configuration space can be accessed by its own
21 Bus, Device and Function Number (Routing ID). And each VF also has PCI
22 Memory Space, which is used to map its register set. VF device driver
38 enables per-PF, VF enable/disable values versus the first method,
44 The second method is the recommended method for new/future VF devices.
48 The VF is treated as hot-plugged PCI devices in the kernel, so they
49 should be able to work in the same way as real PCI devices. The VF
/Linux-v4.19/Documentation/networking/
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.
Dnetvsc.txt52 Virtual Function (VF) device is passed to the guest as a PCI
53 device. In this case, both a synthetic (netvsc) and VF device are
56 The VF is enslaved by netvsc device. The netvsc driver will transparently
57 switch the data path to the VF when it is available and up.
62 VF slave device.
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.
Di40e.txt80 which VF. Note that 0 is the PF, so the VF identifier is offset by 1. For
86 2 of that VF.
159 Spoof event(s) detected on VF (n)
161 Where n=the VF that attempted to do the spoofing.
Digb.txt104 Spoof event(s) detected on VF(n)
106 Where n=the VF that attempted to do the spoofing.
110 You can set a MAC address of a Virtual Function (VF), a default VLAN and the
Dixgbe.txt296 Spoof event(s) detected on VF (n)
298 Where n=the VF that attempted to do the spoofing.
320 While direct assignment of a PCIe device or an SR-IOV Virtual Function (VF)
Dena.txt18 SR-IOV Physical Function (PF) and Virtual Function (VF) devices.
42 1d0f:ec20 - ENA VF
43 1d0f:ec21 - ENA VF with LLQ support
D00-INDEX126 - README for the Intel Virtual Function (VF) Driver (ixgbevf).
/Linux-v4.19/drivers/media/platform/mtk-mdp/
Dmtk_mdp_regs.c22 #define MDP_COLORFMT_PACK(VIDEO, PLANE, COPLANE, HF, VF, BITS, GROUP, SWAP, ID)\ argument
24 ((HF) << 20) | ((VF) << 18) | ((BITS) << 8) | ((GROUP) << 6) |\
/Linux-v4.19/Documentation/devicetree/bindings/media/xilinx/
Dvideo.txt21 AXI bus between video IP cores, using its VF code as defined in "AXI4-Stream
/Linux-v4.19/tools/build/
DMakefile.feature221 ifeq ($(VF),1)
/Linux-v4.19/drivers/net/ethernet/cavium/
DKconfig92 tristate "Cavium LiquidIO VF support"
/Linux-v4.19/Documentation/ABI/testing/
Ddebugfs-driver-genwqe70 Description: Default VF timeout 250ms. Testing might require 1000ms.
/Linux-v4.19/drivers/net/ethernet/hisilicon/
DKconfig113 This selects the HNS3 VF drivers network acceleration engine & its hardware
/Linux-v4.19/Documentation/ABI/stable/
Dsysfs-class-infiniband412 Enabling QP0 on VFs for selected VF/port. By default, no VFs are
416 for the indicated VF/port
420 indicated VF/port. 0 = disable, 1 = enable.
422 The requested enablement will occur at the next reset of the VF
423 (e.g. driver restart on the VM which owns the VF).
/Linux-v4.19/Documentation/scsi/
Dscsi_fc_transport.txt42 (just like a normal non-NPIV adapter). Using the Virtual Fabric (VF)
47 used together with VF so that the port can obtain multiple N_Port_IDs
65 vports. However, consideration was given to VF-based vports and it
DChangeLog.megaraid_sas11 3. Fix LD/VF affiliation parsing.
25 4. Add Dell PowerEdge VRTX SR-IOV VF device support.
178 4. Use lowest memory bar (for SR-IOV VF support).
/Linux-v4.19/net/
DKconfig444 VF as an accelerated low latency datapath. It also allows live
446 paravirtual datapath when the VF is unplugged.
/Linux-v4.19/drivers/mtd/devices/
DKconfig88 Spansion S25SL, SST 25VF, ST M25P, and Winbond W25X. Other chips
/Linux-v4.19/drivers/net/
DKconfig523 a VM with direct attached VF by failing over to the paravirtual
524 datapath when the VF is unplugged.
/Linux-v4.19/drivers/net/ethernet/qlogic/qed/
Dqed_cxt.c714 qed_cxt_set_blk(&p_cli->vf_blks[CDUT_FL_SEG_BLK(0, VF)]); in qed_cxt_cfg_ilt_compute()
735 p_blk = &p_cli->vf_blks[CDUT_FL_SEG_BLK(0, VF)]; in qed_cxt_cfg_ilt_compute()
/Linux-v4.19/tools/perf/
DMakefile.config984 ifeq ($(VF),1)