| /Linux-v6.6/tools/testing/selftests/bpf/prog_tests/ |
| D | cgroup_attach_override.c | 8 #define BAR "/foo/bar/" macro
55 bar = test__join_cgroup(BAR); in serial_test_cgroup_attach_override()
66 "attach prog to %s failed, errno=%d\n", BAR, errno)) in serial_test_cgroup_attach_override()
74 "detach prog from %s failed, errno=%d\n", BAR, errno)) in serial_test_cgroup_attach_override()
84 "attach prog to %s failed, errno=%d\n", BAR, errno)) in serial_test_cgroup_attach_override()
98 "attach prog to %s failed, errno=%d\n", BAR, errno)) in serial_test_cgroup_attach_override()
103 "attach prog to %s unexpectedly succeeded\n", BAR)) in serial_test_cgroup_attach_override()
108 "detach prog from %s failed, errno=%d\n", BAR, errno)) in serial_test_cgroup_attach_override()
123 "attach prog to %s unexpectedly succeeded\n", BAR)) in serial_test_cgroup_attach_override()
129 "attach prog to %s unexpectedly succeeded\n", BAR)) in serial_test_cgroup_attach_override()
|
| /Linux-v6.6/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
|
| /Linux-v6.6/Documentation/gpu/rfc/ |
| D | i915_small_bar.rst | 2 I915 Small BAR RFC Section
4 Starting from DG2 we will have resizable BAR support for device local-memory(i.e
5 I915_MEMORY_CLASS_DEVICE), but in some cases the final BAR size might still be
14 underneath the device has a small BAR, meaning only some portion of it is CPU
41 1) Error capture is best effort on small BAR systems; if the pages are not
|
| /Linux-v6.6/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
|
| /Linux-v6.6/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
|
| /Linux-v6.6/Documentation/PCI/endpoint/ |
| D | pci-ntb-function.rst | 117 the outbound ATU such that transactions to Doorbell BAR will be routed
128 will configure the outbound ATU such that transactions to MW BAR
155 same BAR. The initial portion of the region will have doorbell
166 same BAR. The initial portion of the region will have config region
177 Used to determine the offset within the DB BAR that should be written
233 If one 32-bit BAR is allocated for each of these regions, the scheme would
237 BAR NO CONSTRUCTS USED
247 However if we allocate a separate BAR for each of the regions, there would not
259 BAR NO CONSTRUCTS USED
|
| D | pci-vntb-function.rst | 106 BAR NO CONSTRUCTS USED
119 BAR NO CONSTRUCTS USED
|
| 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
|
| /Linux-v6.6/Documentation/translations/zh_CN/PCI/ |
| D | acpi-info.rst | 25 发现它们，使用配置访问来发现和识别设备，并读取和测量它们的BAR。然而，如果ACPI为它们
29 ACPI资源描述是通过ACPI命名空间中设备的_CRS对象完成的[2]。_CRS就像一个通用的PCI BAR：
|
| D | pci.rst | 244 范围）和 ``request_region()`` （用于IO端口范围）。对于那些不被 "正常 "PCI BAR描
|
| /Linux-v6.6/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
537 depends on BAR && m
[all …]
|
| /Linux-v6.6/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)
|
| /Linux-v6.6/Documentation/translations/zh_CN/userspace-api/accelerators/ |
| D | ocxl.rst | 68 设备被扫描并且BAR（基址寄存器）被分配。像“lspci”的命令因此可以被用于查看
|
| /Linux-v6.6/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)
|
| /Linux-v6.6/drivers/firmware/broadcom/ |
| D | Kconfig | 21 a PCI BAR.
|
| /Linux-v6.6/Documentation/accel/qaic/ |
| D | aic100.rst | 45 * The first BAR is 4K in size, and exposes the MHI interface to the host.
47 * The second BAR is 2M in size, and exposes the DMA Bridge interface to the
50 * The third BAR is variable in size based on an individual AIC100's
51 configuration, but defaults to 64K. This BAR currently has no purpose.
258 DBC registers are exposed to the host via the second BAR. Each DBC consumes
259 4KB of space in the BAR.
|
| /Linux-v6.6/Documentation/driver-api/ |
| D | men-chameleon-bus.rst | 67 header lists the device id, PCI BAR, offset from the beginning of the PCI
68 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
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-bus-pci | 475 These files provide an interface to PCIe Resizable BAR support.
476 A file is created for each BAR resource (N) supported by the
477 PCIe Resizable BAR extended capability of the device. Reading
483 The bitmap represents supported resource sizes for the BAR,
485 example the device supports 64MB, 128MB, and 256MB BAR sizes.
|
| /Linux-v6.6/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | switchdev.rst | 79 A subfunction has a dedicated window in PCI BAR space that is not shared
82 PCI BAR space.
|
| /Linux-v6.6/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.
|
| /Linux-v6.6/Documentation/arch/arm/ |
| D | ixp4xx.rst | 79 To access PCI via this space, we simply ioremap() the BAR
|
| /Linux-v6.6/Documentation/arch/x86/ |
| D | earlyprintk.rst | 35 Capabilities: [58] Debug port: BAR=1 offset=00a0
|
