Home
last modified time | relevance | path

Searched refs:BAR (Results 1 – 25 of 55) sorted by relevance

123

/openbmc/openbmc/poky/meta/lib/oeqa/runtime/cases/
H A Dparselogs-ignores-qemuall.txt9 # pci 0000:00:00.0: [Firmware Bug]: reg 0x10: invalid BAR (can't size)
10 # pci 0000:00:00.0: [Firmware Bug]: reg 0x14: invalid BAR (can't size)
11 # pci 0000:00:00.0: [Firmware Bug]: reg 0x18: invalid BAR (can't size)
12 # pci 0000:00:00.0: [Firmware Bug]: reg 0x1c: invalid BAR (can't size)
13 # pci 0000:00:00.0: [Firmware Bug]: reg 0x20: invalid BAR (can't size)
14 # pci 0000:00:00.0: [Firmware Bug]: reg 0x24: invalid BAR (can't size)
15 invalid BAR (can't size)
16 # 6.10+ the invalid BAR warnings are of this format:
17 # pci 0000:00:00.0: [Firmware Bug]: BAR 0: invalid; can't size
18 # pci 0000:00:00.0: [Firmware Bug]: BAR 1: invalid; can't size
[all …]
H A Dparselogs-ignores-mipsarch.txt11 # pci 0000:00:00.0: BAR 2: can't handle BAR above 4GB (bus address 0x1f00000010)
12 # pci 0000:00:00.0: BAR 5: error updating (0x1105d034 != 0x0100d034)
13 BAR 0: error updating
14 BAR 1: error updating
15 BAR 2: error updating
16 BAR 3: error updating
17 BAR 4: error updating
18 BAR 5: error updating
19 : can't handle BAR above 4GB
H A Dparselogs-ignores-qemuppc.txt5 can't handle BAR above 4GB
/openbmc/linux/tools/testing/selftests/bpf/prog_tests/
H A Dcgroup_attach_override.c8 #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()
/openbmc/qemu/docs/specs/
H A Dpci-testdev.rst8 Each of BAR 0+1 can be memory or IO. Guests must detect
9 BAR types and act accordingly.
11 BAR 0+1 size is up to 4K bytes each.
12 BAR 0+1 starts with the following header:
21 * any other value if test not supported on this BAR
24 uint32_t offset; /* read-only, offset in this BAR for a given test */
32 The device is expected to always implement tests 0 to N on each BAR, and to add new
34 detects an access type that it does not support on this BAR, then stop.
36 BAR2 is a 64bit memory BAR, without backing storage. It is disabled
/openbmc/linux/Documentation/powerpc/
H A Dpci_iov_resource_on_powernv.rst172 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 …]
/openbmc/linux/Documentation/gpu/rfc/
H A Di915_small_bar.rst2 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
/openbmc/qemu/docs/
H A Dpcie_sriov.txt22 A virtual function is different from a physical function in that the BAR
23 space for all VFs are defined by the BAR registers in the PFs SR/IOV
24 capability. All VFs have the same BARs and BAR sizes.
28 <VF BAR start> + <VF number> * <BAR sz> + <offset>
31 setting up a BAR for a VF.
/openbmc/qemu/hw/remote/
H A Dtrace-events12 vfu_bar_register(int i, uint64_t addr, uint64_t size) "vfu: BAR %d: addr 0x%"PRIx64" size 0x%"PRIx6…
13 vfu_bar_rw_enter(const char *op, uint64_t addr) "vfu: %s request for BAR address 0x%"PRIx64""
14 vfu_bar_rw_exit(const char *op, uint64_t addr) "vfu: Finished %s of BAR address 0x%"PRIx64""
/openbmc/linux/drivers/ntb/hw/idt/
H A DKconfig21 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
/openbmc/linux/Documentation/misc-devices/
H A Dpci-endpoint-test.rst15 #) verifying addresses programmed in BAR
31 Tests the BAR. The number of the BAR to be tested
/openbmc/linux/Documentation/PCI/endpoint/
H A Dpci-ntb-function.rst117 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
H A Dpci-vntb-function.rst106 BAR NO CONSTRUCTS USED
119 BAR NO CONSTRUCTS USED
H A Dpci-endpoint.rst49 * 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
/openbmc/linux/Documentation/translations/zh_CN/PCI/
H A Dacpi-info.rst25 发现它们，使用配置访问来发现和识别设备，并读取和测量它们的BAR。然而，如果ACPI为它们
29 ACPI资源描述是通过ACPI命名空间中设备的_CRS对象完成的[2]。_CRS就像一个通用的PCI BAR：
/openbmc/linux/Documentation/kbuild/
H A Dkconfig-language.rst124 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 …]
/openbmc/linux/Documentation/devicetree/bindings/i2c/
H A Di2c-pxa-pci-ce4100.txt21 offset from be base of the BAR (which would be
23 the same BAR)
/openbmc/qemu/qapi/
H A Dcommon.json74 # An enumeration of options for specifying a PCI BAR
78 # @auto: The PCI BAR for the feature is automatically selected
/openbmc/linux/Documentation/translations/zh_CN/userspace-api/accelerators/
H A Docxl.rst68 设备被扫描并且BAR（基址寄存器）被分配。像“lspci”的命令因此可以被用于查看
/openbmc/linux/Documentation/driver-api/pci/
H A Dp2pdma.rst60 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)
/openbmc/linux/drivers/firmware/broadcom/
H A DKconfig21 a PCI BAR.
/openbmc/qemu/docs/devel/
H A Dvfio-iommufd.rst146 BAR region yet. Below warning shows for assigned PCI device, it's not a bug.
150 qemu-system-x86_64: warning: IOMMU_IOAS_MAP failed: Bad address, PCI BAR?
H A Dmemory.rst60 into one unit. For example, a PCI BAR may be composed of a RAM region
336 In addition the vram is mapped as a BAR at address e1000000, and an additional
337 BAR containing MMIO registers is mapped after it.
339 Note that if the guest maps a BAR outside the PCI hole, it would not be
/openbmc/linux/Documentation/accel/qaic/
H A Daic100.rst45 * 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.
/openbmc/linux/Documentation/driver-api/
H A Dmen-chameleon-bus.rst67 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

123