Home
last modified time | relevance | path

Searched refs:PF (Results 1 – 25 of 66) sorted by relevance

123

/Linux-v6.6/tools/testing/selftests/x86/
Dtest_FCOMI.c19 PF = 1 << 2, enumerator
21 ARITH = CF | PF | ZF,
111 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in test_qnan()
140 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testu_qnan()
171 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testu_snan()
254 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testp_qnan()
282 if ((res_fcomi_nan_1 & ARITH) != (ZF|CF|PF)) { in testup_qnan()
316 err |= test(CF|ZF|PF); in main()
317 err |= test_qnan(CF|ZF|PF); in main()
318 err |= testu_qnan(CF|ZF|PF); in main()
[all …]
Dtest_FCMOV.c44 PF = 1 << 2, enumerator
83 err |= !(fcmovb(PF) == 1.0); err |= !(fcmovnb(PF) != 1.0); in main()
84 err |= !(fcmove(PF) == 1.0); err |= !(fcmovne(PF) != 1.0); in main()
85 err |= !(fcmovbe(PF) == 1.0); err |= !(fcmovnbe(PF) != 1.0); in main()
86 err |= !(fcmovu(PF) != 1.0); err |= !(fcmovnu(PF) == 1.0); in main()
/Linux-v6.6/drivers/pinctrl/freescale/
Dpinctrl-imx27.c24 #define PF 5 macro
177 MX27_PAD_NFRB = PAD_ID(PF, 0),
178 MX27_PAD_NFCLE = PAD_ID(PF, 1),
179 MX27_PAD_NFWP_B = PAD_ID(PF, 2),
180 MX27_PAD_NFCE_B = PAD_ID(PF, 3),
181 MX27_PAD_NFALE = PAD_ID(PF, 4),
182 MX27_PAD_NFRE_B = PAD_ID(PF, 5),
183 MX27_PAD_NFWE_B = PAD_ID(PF, 6),
184 MX27_PAD_PC_POE = PAD_ID(PF, 7),
185 MX27_PAD_PC_RW_B = PAD_ID(PF, 8),
[all …]
/Linux-v6.6/Documentation/translations/zh_CN/PCI/
Dpci-iov-howto.rst32 虚拟设备。物理设备被称为物理功能（PF），而虚拟设备被称为虚拟功能（VF）。VF的分
33 配可以由PF通过封装在该功能中的寄存器动态控制。默认情况下，该功能未被启用，PF表
45 有多种方法可用于SR-IOV的启用。在第一种方法中，设备驱动（PF驱动）将通过SR-IOV
46 核心提供的API控制功能的启用和禁用。如果硬件具有SR-IOV能力，加载其PF驱动器将启
47 用它和与PF相关的所有VF。一些PF驱动需要设置一个模块参数，以确定要启用的VF的数量。
48 在第二种方法中，对sysfs文件sriov_numvfs的写入将启用和禁用与PCIe PF相关的VF。
49 这种方法实现了每个PF的VF启用/禁用值，而第一种方法则适用于同一设备的所有PF。此外，
/Linux-v6.6/Documentation/ABI/testing/
Ddebugfs-hisi-hpre5 Only available for PF.
12 Only available for PF.
21 Only available for PF.
26 Description: One HPRE controller has one PF and multiple VFs, each function
28 Only available for PF.
33 Description: The <bdf> is related the function for PF and VF.
44 Only available for PF.
50 Available for PF and VF in host. VF in guest currently only
58 Only available for PF.
67 Only available for PF.
[all …]
Ddebugfs-hisi-zip5 Only available for PF.
11 Only available for PF.
20 Only available for PF.
25 Description: One ZIP controller has one PF and multiple VFs, each function
27 Only available for PF.
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
51 Only available for PF.
60 Only available for PF.
67 Available for both PF and VF, and take no other effect on ZIP.
[all …]
Ddebugfs-driver-genwqe10 Only available for PF.
16 Only available for PF.
22 Only available for PF.
28 Only available for PF.
35 Only available for PF.
41 Only available for PF.
47 Only available for PF.
53 Only available for PF.
79 Only available for PF.
84 Description: Dump job timeout register values for PF and VFs.
[all …]
Ddebugfs-hisi-sec7 Only available for PF, and take no other effect on SEC.
12 Description: One SEC controller has one PF and multiple VFs, each function
15 Only available for PF.
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
39 Only available for PF.
47 Only available for PF, and take no other effect on SEC.
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.
[all …]
/Linux-v6.6/arch/m68k/68000/
Ddragen2.c59 PFSEL |= PF(5); /* select pin as I/O */ in init_dragen2()
60 PFDIR |= PF(5); /* select pin as output */ in init_dragen2()
61 PFDATA &= ~PF(5); /* set pin low */ in init_dragen2()
64 PFDATA |= PF(5); in init_dragen2()
66 PFDATA &= ~PF(5); in init_dragen2()
/Linux-v6.6/Documentation/networking/device_drivers/ethernet/marvell/
Docteontx2.rst28 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.
51 - Number of VFs per PF are either static or configurable at compile time.
53 - Also assigns MSIX vectors to each of PF and VFs.
59 Linux kernel will have multiple drivers registering to different PF and VFs
70 PF/VFs communicates with AF via a shared memory region (mailbox). Upon
85 - Map a physical link to a RVU PF to which a netdev is registered.
86 - Attach NIX and NPA block LFs to RVU PF/VF which provide buffer pools, RQs, SQs
104 This RVU PF handles IO, is mapped to a physical ethernet link and this
[all …]
/Linux-v6.6/Documentation/PCI/
Dpci-iov-howto.rst20 devices. The physical device is referred to as Physical Function (PF)
22 Allocation of the VF can be dynamically controlled by the PF via
24 not enabled and the PF behaves as traditional PCIe device. Once it's
38 In the first method, the device driver (PF driver) will control the
40 If the hardware has SR-IOV capability, loading its PF driver would
41 enable it and all VFs associated with the PF. Some PF drivers require
44 enable and disable the VFs associated with a PCIe PF. This method
45 enables per-PF, VF enable/disable values versus the first method,
/Linux-v6.6/drivers/net/ethernet/freescale/enetc/
DKconfig5 This module supports common functionality between the PF and VF
11 tristate "ENETC PF driver"
22 physical function (PF) devices, managing ENETC Ports at a privileged
36 virtual function (VF) devices enabled by the ENETC PF driver.
53 physical function (PF) device.
/Linux-v6.6/Documentation/networking/device_drivers/ethernet/intel/
Diavf.rst27 (PF) driver compiled with CONFIG_PCI_IOV. The iavf driver requires
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,
90 adapt to changing feature sets of the physical function driver (PF) with which
91 it is associated. This allows system administrators to update a PF without
96 additional features depending on what features are available in the PF with
109 configured through the PF
114 - HW mailbox is used for VF to PF communications (including on Windows)
148 - Depending on the underlying PF device, ADQ cannot be enabled when the
212 - If a TC filter on a PF matches traffic over a VF (on the PF), that traffic
[all …]
Dice.rst72 from the administrative interface on the PF. This configuration allows
148 - You cannot update the DDP package if any PF drivers are already loaded. To
152 - Only the first loaded PF per device can download a package for that device.
385 Accelerated Receive Flow Steering (aRFS) on the PF. aRFS is a load-balancing
477 how many VFs each PF supports, use the following command::
485 Displaying VF Statistics on the PF
487 Use the following command to display the statistics for the PF and its VFs::
494 The PF driver will display a subset of the statistics for the PF and for all
495 VFs that are configured. The PF will always print a statistics block for each
511 For example, the following will configure PF eth0 and the first VF on VLAN 10::
[all …]
/Linux-v6.6/drivers/gpu/drm/i915/gt/uc/
Dintel_guc_capture.c176 MAKE_REGLIST(gen8_global_regs, PF, GLOBAL, 0),
177 MAKE_REGLIST(gen8_rc_class_regs, PF, ENGINE_CLASS, GUC_CAPTURE_LIST_CLASS_RENDER_COMPUTE),
178 MAKE_REGLIST(gen8_rc_inst_regs, PF, ENGINE_INSTANCE, GUC_CAPTURE_LIST_CLASS_RENDER_COMPUTE),
179 MAKE_REGLIST(empty_regs_list, PF, ENGINE_CLASS, GUC_CAPTURE_LIST_CLASS_VIDEO),
180 MAKE_REGLIST(gen8_vd_inst_regs, PF, ENGINE_INSTANCE, GUC_CAPTURE_LIST_CLASS_VIDEO),
181 MAKE_REGLIST(empty_regs_list, PF, ENGINE_CLASS, GUC_CAPTURE_LIST_CLASS_VIDEOENHANCE),
182 MAKE_REGLIST(gen8_vec_inst_regs, PF, ENGINE_INSTANCE, GUC_CAPTURE_LIST_CLASS_VIDEOENHANCE),
183 MAKE_REGLIST(empty_regs_list, PF, ENGINE_CLASS, GUC_CAPTURE_LIST_CLASS_BLITTER),
184 MAKE_REGLIST(gen8_blt_inst_regs, PF, ENGINE_INSTANCE, GUC_CAPTURE_LIST_CLASS_BLITTER),
185 MAKE_REGLIST(empty_regs_list, PF, ENGINE_CLASS, GUC_CAPTURE_LIST_CLASS_GSC_OTHER),
[all …]
/Linux-v6.6/Documentation/networking/devlink/
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.
/Linux-v6.6/Documentation/admin-guide/perf/
Dhns3-pmu.rst106 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-v6.6/arch/m68k/include/asm/
DMC68328.h561 #define PF(x) (1 << (x)) macro
562 #define PF_A(x) PF((x) - 24) /* This is Port F specific only */
564 #define PF_A24 PF(0) /* Use A24 as PF(0) */
565 #define PF_A25 PF(1) /* Use A25 as PF(1) */
566 #define PF_A26 PF(2) /* Use A26 as PF(2) */
567 #define PF_A27 PF(3) /* Use A27 as PF(3) */
568 #define PF_A28 PF(4) /* Use A28 as PF(4) */
569 #define PF_A29 PF(5) /* Use A29 as PF(5) */
570 #define PF_A30 PF(6) /* Use A30 as PF(6) */
571 #define PF_A31 PF(7) /* Use A31 as PF(7) */
/Linux-v6.6/arch/arm/boot/dts/allwinner/
Dsun8i-r16-nintendo-nes-classic.dts24 * UART0 is available on two ports: PB and PF, both are accessible.
25 * PF can also be used for the SD card so PB is preferred.
/Linux-v6.6/Documentation/admin-guide/mm/
Dsoft-dirty.rst24 modify a page at some virtual address the #PF occurs and the kernel sets
28 soft-dirty bits clear, the #PF-s that occur after that are processed fast.
33 While in most cases tracking memory changes by #PF-s is more than enough
/Linux-v6.6/drivers/tty/
Dn_gsm.c367 #define PF 0x10 macro
714 if ((control & ~PF) == UI || (control & ~PF) == UIH) in gsm_print_packet()
719 switch (control & ~PF) { in gsm_print_packet()
757 if (control & PF) in gsm_print_packet()
986 switch (msg->ctrl & ~PF) { in gsm_is_flow_ctrl_msg()
992 switch (cmd & ~PF) { in gsm_is_flow_ctrl_msg()
1114 if (msg->ctrl == UI || msg->ctrl == (UI|PF)) in __gsm_data_queue()
1127 switch (msg->ctrl & ~PF) { in __gsm_data_queue()
1777 gsm_command(gsm, dlci->addr, SABM|PF); in gsm_control_negotiation()
2245 gsm_command(dlci->gsm, dlci->addr, SABM|PF); in gsm_dlci_t1()
[all …]
/Linux-v6.6/net/netfilter/ipset/
Dip_set_hash_ipmac.c78 #define PF 4 macro
185 #undef PF
190 #define PF 6 macro
/Linux-v6.6/Documentation/networking/
Drepresentors.rst27 the virtual functions appear in the networking stack of the PF via the
28 representors. The PF can thus always communicate freely with the virtual
30 The PF can configure standard Linux forwarding between representors, the uplink
45 Typically, this will be a PF, but conceivably a NIC could be configured to grant
103 as a vDPA virtio-blk PF backed by remote/distributed storage), if (and only
108 their own port on the switch (as opposed to using their parent PF's port).
111 PF or VF.
138 DMA requests unchanged to another PF whose driver then initiates and
140 run over the virtual switch and the virtio-blk PF should thus *not* have a
/Linux-v6.6/Documentation/networking/device_drivers/ethernet/amd/
Dpds_vdpa.rst18 services. It depends on the ``pds_core`` driver and hardware for the PF
41 # Enable vDPA VF auxiliary device(s) in the PF
/Linux-v6.6/Documentation/fpga/
Ddfl.rst210 - Assign port to PF (DFL_FPGA_FME_PORT_ASSIGN)
211 - Release port from PF (DFL_FPGA_FME_PORT_RELEASE)
384 | PF | | VF |
402 FME is always accessed through the physical function (PF).
404 Ports (and related AFUs) are accessed via PF by default, but could be exposed
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
441 provides ioctls to release Port from PF and assign Port to PF. After release
442 a port from PF, then it's safe to expose this port through a VF via PCIe SRIOV
[all …]

123