/kernel/linux/linux-5.10/tools/testing/selftests/bpf/prog_tests/ |
D | cgroup_attach_override.c | 8 #define BAR "/foo/bar/" macro 55 bar = test__join_cgroup(BAR); in test_cgroup_attach_override() 66 "attach prog to %s failed, errno=%d\n", BAR, errno)) in test_cgroup_attach_override() 74 "detach prog from %s failed, errno=%d\n", BAR, errno)) in test_cgroup_attach_override() 84 "attach prog to %s failed, errno=%d\n", BAR, errno)) in test_cgroup_attach_override() 98 "attach prog to %s failed, errno=%d\n", BAR, errno)) in test_cgroup_attach_override() 103 "attach prog to %s unexpectedly succeeded\n", BAR)) in test_cgroup_attach_override() 108 "detach prog from %s failed, errno=%d\n", BAR, errno)) in test_cgroup_attach_override() 123 "attach prog to %s unexpectedly succeeded\n", BAR)) in test_cgroup_attach_override() 129 "attach prog to %s unexpectedly succeeded\n", BAR)) in test_cgroup_attach_override()
|
/kernel/linux/linux-5.10/Documentation/powerpc/ |
D | pci_iov_resource_on_powernv.rst | 172 discover the BAR sizes and assign addresses for them. For VF devices, 173 software uses VF BAR registers in the *PF* SR-IOV Capability to 177 When a VF BAR in the PF SR-IOV Capability is programmed, it sets the 180 1MB VF BAR0, the address in that VF BAR sets the base of an 8MB region. 182 is a BAR0 for one of the VFs. Note that even though the VF BAR 195 the segment size matches the smallest VF BAR, which means larger VF 210 and different segment sizes. If we have VFs that each have a 1MB BAR 211 and a 32MB BAR, we could use one M64 window to assign 1MB segments and 215 more in the next two sections. For a given VF BAR, we need to 216 effectively reserve the entire 256 segments (256 * VF BAR size) and [all …]
|
D | eeh-pci-error-recovery.rst | 95 config space (the base address registers (BAR's), latency timer, 177 It saves the device BAR's and then calls rpaphp_unconfig_pci_adapter(). 183 It then resets the PCI card, reconfigures the device BAR's, and
|
/kernel/linux/linux-5.10/drivers/ntb/hw/idt/ |
D | Kconfig | 21 accepted by a BAR. Note that BAR0 must map PCI configuration space 25 BAR settings of peer NT-functions, the BAR setups can't be done over
|
/kernel/linux/linux-5.10/Documentation/misc-devices/ |
D | pci-endpoint-test.rst | 15 #) verifying addresses programmed in BAR 31 Tests the BAR. The number of the BAR to be tested
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/ |
D | i2c-pxa-pci-ce4100.txt | 21 offset from be base of the BAR (which would be 23 the same BAR)
|
/kernel/linux/linux-5.10/Documentation/PCI/endpoint/ |
D | pci-endpoint.rst | 49 * set_bar: ops to configure the BAR 50 * clear_bar: ops to reset the BAR 102 the BAR. 188 The PCI Function driver can allocate space for a particular BAR using
|
D | pci-test-howto.rst | 145 BAR tests
|
/kernel/linux/linux-5.10/drivers/staging/gasket/ |
D | TODO | 8 the gasket APIs adds some extra conveniences like PCI BAR mapping, and
|
/kernel/linux/linux-5.10/Documentation/kbuild/ |
D | kconfig-language.rst | 124 bool "foo" if BAR 125 default y if BAR 129 depends on BAR 147 if FOO depends on BAR that is not set. 167 depends on BAR 172 FOO BAR BAZ's default choice for BAZ 187 Note: If the combination of FOO=y and BAR=m causes a link error, 198 FOO should imply not only BAZ, but also its dependency BAR:: 202 imply BAR 552 depends on BAR && m
|
/kernel/linux/linux-5.10/drivers/firmware/broadcom/ |
D | Kconfig | 21 a PCI BAR.
|
/kernel/linux/linux-5.10/Documentation/driver-api/pci/ |
D | p2pdma.rst | 60 functionality. For example, if a specific RNIC added a BAR with some 69 A provider simply needs to register a BAR (or a portion of a BAR)
|
/kernel/linux/linux-5.10/Documentation/driver-api/ |
D | men-chameleon-bus.rst | 66 header lists the device id, PCI BAR, offset from the beginning of the PCI 67 BAR, size in the FPGA, interrupt number and some other properties currently
|
D | switchtec.rst | 97 NT EP BAR 2 will be dynamically configured as a Direct Window, and
|
/kernel/linux/linux-5.10/Documentation/scsi/ |
D | ChangeLog.sym53c8xx | 37 - Get both the BAR cookies used by CPU and actual PCI BAR 40 BAR values to destination address to make decision. 44 PCI BAR value from the BAR cookie is now useless.
|
D | ChangeLog.ncr53c8xx | 10 - Get both the BAR cookies actual and PCI BAR values.
|
/kernel/linux/linux-5.10/Documentation/arm/ |
D | ixp4xx.rst | 79 To access PCI via this space, we simply ioremap() the BAR
|
/kernel/linux/linux-5.10/Documentation/x86/ |
D | earlyprintk.rst | 35 Capabilities: [58] Debug port: BAR=1 offset=00a0
|
/kernel/linux/linux-5.10/arch/arm/mach-ixp4xx/ |
D | Kconfig | 219 To access PCI via this space, we simply ioremap() the BAR
|
/kernel/linux/linux-5.10/Documentation/core-api/ |
D | dma-api-howto.rst | 68 example, if a PCI device has a BAR, the kernel reads the bus address (A) 69 from the BAR and converts it to a CPU physical address (B). The address B 862 ringp->len = BAR; 867 dma_unmap_len_set(ringp, len, BAR);
|
/kernel/linux/linux-5.10/Documentation/gpu/ |
D | drm-internals.rst | 129 or exists on the PCI device in the ROM BAR. Note that after the ROM has
|
/kernel/linux/linux-5.10/Documentation/mhi/ |
D | mhi.rst | 191 In the case of PCIe, the device is enumerated and assigned BAR-0 for
|
/kernel/linux/linux-5.10/Documentation/driver-api/driver-model/ |
D | devres.rst | 321 pcim_iomap_table() : array of mapped addresses indexed by BAR
|
/kernel/linux/linux-5.10/Documentation/PCI/ |
D | acpi-info.rst | 25 namespace [2]. The _CRS is like a generalized PCI BAR: the OS can read
|
/kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/amazon/ |
D | ena.rst | 146 device memory BAR, which is mapped with write-combine capability.
|