| /Linux-v5.4/tools/testing/selftests/x86/ |
| 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 …]
|
| 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-v5.4/drivers/pinctrl/freescale/ |
| D | pinctrl-imx27.c | 24 #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 …]
|
| D | pinctrl-imx21.c | 20 #define PF 5 macro
144 MX21_PAD_NFRB = PAD_ID(PF, 0),
145 MX21_PAD_NFCE = PAD_ID(PF, 1),
146 MX21_PAD_NFWP = PAD_ID(PF, 2),
147 MX21_PAD_NFCLE = PAD_ID(PF, 3),
148 MX21_PAD_NFALE = PAD_ID(PF, 4),
149 MX21_PAD_NFRE = PAD_ID(PF, 5),
150 MX21_PAD_NFWE = PAD_ID(PF, 6),
151 MX21_PAD_NFIO0 = PAD_ID(PF, 7),
152 MX21_PAD_NFIO1 = PAD_ID(PF, 8),
[all …]
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| 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 …]
|
| 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.
33 Available for PF and VF in host. VF in guest currently only
41 Only available for PF.
50 Only available for PF.
|
| D | sysfs-bus-pci | 237 function (PF) can support. Typically, this is the value reported
238 in the PF's SR-IOV extended capability structure's TotalVFs
250 Functions (VFs) on the physical function (PF). A read of this
251 file will return the number of VFs that are enabled on this PF.
255 of VFs that should be enabled on the PF; the value written
309 This file is associated with the PF of a device that
325 affects only the VFs associated with a specific PF.
|
| /Linux-v5.4/arch/m68k/68000/ |
| D | m68VZ328.c | 80 PFSEL |= PF(5); /* select pin as I/O */ in init_hardware()
81 PFDIR |= PF(5); /* select pin as output */ in init_hardware()
82 PFDATA &= ~PF(5); /* set pin low */ in init_hardware()
85 PFDATA |= PF(5); in init_hardware()
87 PFDATA &= ~PF(5); in init_hardware()
|
| /Linux-v5.4/drivers/staging/unisys/Documentation/ABI/ |
| D | sysfs-platform-visorchipset | 60 PF device is being recovered in another guest.
62 Some SR-IOV devices have problems when the PF is reset without
63 first disabling all VFs attached to that PF. s-Par handles this
65 the script will disable the device. When the PF is recovered,
79 PF device is being recovered in another guest.
81 Some SR-IOV devices have problems when the PF is reset without
82 first disabling all VFs attached to that PF. s-Par handles this
84 the script will disable the device. When the PF is recovered,
|
| /Linux-v5.4/Documentation/PCI/ |
| 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-v5.4/Documentation/networking/device_drivers/intel/ |
| 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 …]
|
| D | ixgbe.rst | 242 Physical Function (PF) and each Virtual Function (VF) is allocated a pool of
255 When VFs are configured, the PF is allocated one pool as well. The PF supports
257 single queue pair. When zero VFs are configured, the PF can support multiple
400 Note that 0 is the PF, so the VF identifier is offset by 1. For example::
441 function (PF). The VF MTU setting cannot be larger than the PF MTU.
494 An interrupt is sent to the PF driver notifying it of the spoof attempt. When a
495 spoofed packet is detected, the PF driver will send the following message to
500 where "x" is the PF interface number; and "n" is number of spoofed packets.
|
| /Linux-v5.4/drivers/net/ethernet/freescale/enetc/ |
| D | Kconfig | 3 tristate "ENETC PF driver"
8 physical function (PF) devices, managing ENETC Ports at a privileged
19 virtual function (VF) devices enabled by the ENETC PF driver.
28 physical function (PF) device.
|
| /Linux-v5.4/arch/m68k/include/asm/ |
| 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-v5.4/Documentation/fpga/ |
| D | dfl.rst | 90 - Assign port to PF (DFL_FPGA_FME_PORT_ASSIGN)
91 - Release port from PF (DFL_FPGA_FME_PORT_RELEASE)
243 | PF | | VF |
261 FME is always accessed through the physical function (PF).
263 Ports (and related AFUs) are accessed via PF by default, but could be exposed
289 | PCI PF Device | | | PCI VF Device |
292 FPGA PCIe device driver is always loaded first once a FPGA PCIe PF or VF device
295 * Finishes enumeration on both FPGA PCIe PF and VF device using common
300 provides ioctls to release Port from PF and assign Port to PF. After release
301 a port from PF, then it's safe to expose this port through a VF via PCIe SRIOV
[all …]
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| 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-v5.4/Documentation/admin-guide/mm/ |
| D | soft-dirty.rst | 26 modify a page at some virtual address the #PF occurs and the kernel sets
30 soft-dirty bits clear, the #PF-s that occur after that are processed fast.
35 While in most cases tracking memory changes by #PF-s is more than enough
|
| /Linux-v5.4/drivers/tty/ |
| D | n_gsm.c | 277 #define PF 0x10 macro
456 switch (control & ~PF) { in gsm_print_packet()
494 if (control & PF) in gsm_print_packet()
742 if (msg->ctrl == UI || msg->ctrl == (UI|PF)) in __gsm_data_queue()
1478 gsm_command(dlci->gsm, dlci->addr, SABM|PF); in gsm_dlci_t1()
1480 } else if (!dlci->addr && gsm->control == (DM | PF)) { in gsm_dlci_t1()
1494 gsm_command(dlci->gsm, dlci->addr, DISC|PF); in gsm_dlci_t1()
1519 gsm_command(dlci->gsm, dlci->addr, SABM|PF); in gsm_dlci_begin_open()
1541 gsm_command(dlci->gsm, dlci->addr, DISC|PF); in gsm_dlci_begin_close()
1750 if ((gsm->control & ~PF) == UI) in gsm_queue()
[all …]
|
| /Linux-v5.4/net/netfilter/ipset/ |
| D | ip_set_hash_ipmac.c | 78 #define PF 4 macro
185 #undef PF
190 #define PF 6 macro
|
| /Linux-v5.4/Documentation/networking/ |
| D | net_failover.rst | 100 PF=enp66s0f0
109 bridge fdb del $MAC dev $PF master
111 ip link set $PF vf $VF_NUM mac $ZERO_MAC
|
| D | hinic.txt | 12 (PF).
25 19e5:1822 - HiNIC PF
58 Management (MGMT) - the PF to MGMT channel that uses API CMD for sending MGMT
|
| /Linux-v5.4/drivers/net/ethernet/marvell/octeontx2/ |
| D | Kconfig | 17 and provides a medium to other PF/VFs to configure HW. Should be
|
| /Linux-v5.4/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | Kconfig | 66 support in ConnectX NIC. MPFs is required for when multi-PF configuration
68 requesting PF.
77 enabled VFs and PF in two available modes:
|
| /Linux-v5.4/Documentation/networking/device_drivers/mellanox/ |
| D | mlx5.rst | 61 | user configured unicast MAC addresses to the requesting PF.
67 | and switching for the enabled VFs and PF in two available modes:
233 NOTE: This command can run only on the PF which has fw tracer ownership,
234 running it on other PF or any VF will return "Operation not permitted".
255 NOTE: This command can run only on PF.
|
| /Linux-v5.4/Documentation/s390/ |
| D | 3270.rst | 235 Some of the Program Function (PF) and Program Attention (PA) keys are
248 No PF key is preassigned to cause a job suspension, but you may cause a
250 assign this function to a PF key. To make PF7 cause job suspension,
266 PF11 rotates forward. You may assign the backward function to any PF
282 Have a command you issue frequently? Assign it to a PF or PA key! Use
|
