| /linux/tools/testing/selftests/x86/ |
| H A D | test_FCOMI.c | 19 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 …]
|
| H A D | test_FCMOV.c | 44 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/Documentation/translations/zh_CN/PCI/ |
| H A D | pci-iov-howto.rst | 32 虚拟设备。物理设备被称为物理功能（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/Documentation/ABI/testing/ |
| H A D | debugfs-hisi-hpre | 5 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 …]
|
| H A D | debugfs-hisi-zip | 5 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 …]
|
| H A D | debugfs-hisi-sec | 7 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 …]
|
| H A D | debugfs-driver-genwqe | 10 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 …]
|
| /linux/arch/m68k/68000/ |
| H A D | dragen2.c | 59 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/Documentation/networking/ |
| H A D | multi-pf-netdev.rst | 5 Multi-PF Netdev
22 The Multi-PF NIC technology enables several CPUs within a multi-socket server to connect directly to
32 The feature adds support for combining multiple PFs of the same port in a Multi-PF environment under
42 Multi-PF or Socket-direct in mlx5 is achieved by grouping PFs together which belong to the same
49 We pick one PF to be a primary (leader), and it fills a special role. The other devices
51 mode, no south <-> north traffic flowing directly through a secondary PF. It needs the assistance of
52 the leader PF (east <-> west traffic) to function. All Rx/Tx traffic is steered through the primary
63 Each combined channel works against one specific PF, creating all its datapath queues against it. We
70 | ch idx | PF idx |
81 mapping between a channel index and a PF is fixed, no matter how many channels the user configures.
[all …]
|
| H A D | representors.rst | 28 the virtual functions appear in the networking stack of the PF via the
29 representors. The PF can thus always communicate freely with the virtual
31 The PF can configure standard Linux forwarding between representors, the uplink
46 Typically, this will be a PF, but conceivably a NIC could be configured to grant
104 as a vDPA virtio-blk PF backed by remote/distributed storage), if (and only
109 their own port on the switch (as opposed to using their parent PF's port).
112 PF or VF.
139 DMA requests unchanged to another PF whose driver then initiates and
141 run over the virtual switch and the virtio-blk PF should thus *not* have a
|
| /linux/Documentation/PCI/ |
| H A D | pci-iov-howto.rst | 20 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/Documentation/misc-devices/ |
| H A D | mrvl_cn10k_dpi.rst | 11 DPI hardware comprises a physical function (PF), its virtual functions,
14 DPI PF function is an administrative function which services the mailbox
18 mrvl_cn10k_dpi.ko misc driver loads on DPI PF device and services the
24 DPI PF driver is just an administrative driver to setup its VF device's
50 how applications use mailbox and ioctl services from DPI PF kernel driver.
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | iavf.rst | 27 (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 …]
|
| H A D | ice.rst | 72 from the administrative interface on the PF. This configuration allows
108 - PF reset - resets only components associated with the given PF, does not
117 - PF reset:
179 - You cannot update the DDP package if any PF drivers are already loaded. To
183 - Only the first loaded PF per device can download a package for that device.
429 Accelerated Receive Flow Steering (aRFS) on the PF. aRFS is a load-balancing
521 how many VFs each PF supports, use the following command::
529 Displaying VF Statistics on the PF
531 Use the following command to display the statistics for the PF and its VFs::
538 The PF driver will display a subset of the statistics for the PF and for all
[all …]
|
| /linux/drivers/net/ethernet/freescale/enetc/ |
| H A D | Kconfig | 6 This module supports common functionality between the PF and VF
15 different versions of NXP ENETC PF controllers.
30 tristate "ENETC PF driver"
42 physical function (PF) devices, managing ENETC Ports at a privileged
48 tristate "ENETC4 PF driver"
75 virtual function (VF) devices enabled by the ENETC PF driver.
92 physical function (PF) device.
|
| /linux/Documentation/networking/device_drivers/ethernet/marvell/ |
| H A D | octeontx2.rst | 29 PF/VF.
45 - A PF/VF with NIX-LF & NPA-LF resources works as a pure network device
46 - A PF/VF with CPT-LF resource works as a pure crypto offload device.
52 - Number of VFs per PF are either static or configurable at compile time.
54 - Also assigns MSIX vectors to each of PF and VFs.
60 Linux kernel will have multiple drivers registering to different PF and VFs
71 PF/VFs communicates with AF via a shared memory region (mailbox). Upon
86 - Map a physical link to a RVU PF to which a netdev is registered.
87 - Attach NIX and NPA block LFs to RVU PF/VF which provide buffer pools, RQs, SQs
105 This RVU PF handles IO, is mapped to a physical ethernet link and this
[all …]
|
| /linux/drivers/gpu/drm/i915/gt/uc/ |
| H A D | intel_guc_capture.c | 172 MAKE_REGLIST(gen8_global_regs, PF, GLOBAL, 0),
173 MAKE_REGLIST(gen8_rc_class_regs, PF, ENGINE_CLASS, GUC_CAPTURE_LIST_CLASS_RENDER_COMPUTE),
174 MAKE_REGLIST(gen8_rc_inst_regs, PF, ENGINE_INSTANCE, GUC_CAPTURE_LIST_CLASS_RENDER_COMPUTE),
175 MAKE_REGLIST(empty_regs_list, PF, ENGINE_CLASS, GUC_CAPTURE_LIST_CLASS_VIDEO),
176 MAKE_REGLIST(gen8_vd_inst_regs, PF, ENGINE_INSTANCE, GUC_CAPTURE_LIST_CLASS_VIDEO),
177 MAKE_REGLIST(empty_regs_list, PF, ENGINE_CLASS, GUC_CAPTURE_LIST_CLASS_VIDEOENHANCE),
178 MAKE_REGLIST(gen8_vec_inst_regs, PF, ENGINE_INSTANCE, GUC_CAPTURE_LIST_CLASS_VIDEOENHANCE),
179 MAKE_REGLIST(empty_regs_list, PF, ENGINE_CLASS, GUC_CAPTURE_LIST_CLASS_BLITTER),
180 MAKE_REGLIST(gen8_blt_inst_regs, PF, ENGINE_INSTANCE, GUC_CAPTURE_LIST_CLASS_BLITTER),
181 MAKE_REGLIST(empty_regs_list, PF, ENGINE_CLASS, GUC_CAPTURE_LIST_CLASS_GSC_OTHER),
[all …]
|
| /linux/Documentation/networking/devlink/ |
| 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.
54 The default rule serves as the primary packet steering rule for a specific PF or VF,
65 The ``octeontx2 PF`` driver implements the following driver-specific parameters.
|
| /linux/arch/m68k/include/asm/ |
| H A D | MC68328.h | 561 #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/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
|
| /linux/Documentation/networking/device_drivers/ethernet/huawei/ |
| H A D | hinic3.rst | 32 19e5:0222 - hinic3 PF/PPF
37 the host. Any PF may serve as a PPF. The PPF is selected dynamically.
80 unsolicited events. Every device, VF or PF, can have up to 4 AEQs.
96 can also be used to post requests and responses between the PF and its VFs.
130 Every function, PF or VF, has a unique ordinal identification within the device.
134 PF is allowed to post management commands to a subordinate VF by specifying the
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | soft-dirty.rst | 24 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/arch/arm/boot/dts/allwinner/ |
| H A D | sun8i-r16-nintendo-nes-classic.dts | 24 * 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/drivers/tty/ |
| H A D | n_gsm.c | 370 #define PF 0x10 macro
718 if ((control & ~PF) == UI || (control & ~PF) == UIH) in gsm_print_packet()
723 switch (control & ~PF) { in gsm_print_packet()
761 if (control & PF) in gsm_print_packet()
990 switch (msg->ctrl & ~PF) { in gsm_is_flow_ctrl_msg()
996 switch (cmd & ~PF) { in gsm_is_flow_ctrl_msg()
1118 if (msg->ctrl == UI || msg->ctrl == (UI|PF)) in __gsm_data_queue()
1131 switch (msg->ctrl & ~PF) { in __gsm_data_queue()
1781 gsm_command(gsm, dlci->addr, SABM|PF); in gsm_control_negotiation()
2246 if (!dlci->addr && gsm->control == (DM | PF)) { in gsm_dlci_t1()
[all …]
|
| /linux/drivers/vfio/pci/virtio/ |
| H A D | Kconfig | 9 SR-IOV PF device to support specific VIRTIO extensions,
26 PCI VF devices. Legacy I/O support requires the SR-IOV PF
|