Home
last modified time | relevance | path

Searched refs:memory (Results 101 – 125 of 5337) sorted by relevance

12345678910>>...214

/openbmc/u-boot/doc/
H A DREADME.memory-test2 hardware, or when using a sloppy port on some board, is memory errors.
4 incorrect initialization of the memory controller. So it appears to
5 be a good idea to always test if the memory is working correctly,
8 U-Boot implements 3 different approaches to perform memory tests:
14 memory banks on this piece of hardware. The code is supposed to be
17 catch 99% of hardware related (i. e. reliably reproducible) memory
23 This is probably the best known memory test utility in U-Boot.
35 no knowledge about memory ranges that may be in use for other
46 system memory) and for U-Boot (code, data, etc. - see above;
69 It should pointed out that _all_ these memory tests have one
[all …]
/openbmc/u-boot/doc/device-tree-bindings/memory/
H A Dmemory.txt3 The memory binding for U-Boot is as in the ePAPR with the following additions:
5 Optional subnodes can be used defining the memory layout for different board
11 If subnodes are present, then the /memory node must define these properties:
19 memory-banks - list of memory banks in the same format as normal
37 memory {
65 * Default of 2GB of memory, auto-sized, so could be smaller
66 * 3.5GB of memory (with no auto-size) if (board id & 2) is 2
67 * 1GB of memory (with no auto-size) if board id is 17.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-bsp/flashrom/flashrom/
H A D0001-hwaccess-use-__asm__-as-is-done-elsewhere.patch12 74 | asm("eieio" : : : "memory");
15 74 | asm("eieio" : : : "memory");
29 …ps://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/memory-barriers.txt
32 - asm("eieio" : : : "memory");
33 + __asm__ ("eieio" : : : "memory");
36 …/* Sparc V9 CPUs support three different memory orderings that range from x86-like TSO to PowerPC-…
38 * use the strongest hardware memory barriers that exist on Sparc V9. */
39 - asm volatile ("membar #Sync" ::: "memory");
40 + __asm__ volatile ("membar #Sync" ::: "memory");
/openbmc/linux/drivers/gpu/drm/nouveau/nvkm/core/
H A Dgpuobj.c50 return nvkm_memory_map(gpuobj->memory, offset, vmm, vma, argv, argc); in nvkm_gpuobj_heap_map()
56 return nvkm_ro32(gpuobj->memory, offset); in nvkm_gpuobj_heap_rd32()
62 nvkm_wo32(gpuobj->memory, offset, data); in nvkm_gpuobj_heap_wr32()
70 nvkm_done(gpuobj->memory); in nvkm_gpuobj_heap_release()
92 gpuobj->map = nvkm_kmap(gpuobj->memory); in nvkm_gpuobj_heap_acquire()
202 abs(align), zero, &gpuobj->memory); in nvkm_gpuobj_ctor()
207 gpuobj->addr = nvkm_memory_addr(gpuobj->memory); in nvkm_gpuobj_ctor()
208 gpuobj->size = nvkm_memory_size(gpuobj->memory); in nvkm_gpuobj_ctor()
222 nvkm_memory_unref(&gpuobj->memory); in nvkm_gpuobj_del()
255 (*pgpuobj)->addr = nvkm_memory_addr(memory); in nvkm_gpuobj_wrap()
[all …]
/openbmc/linux/Documentation/devicetree/bindings/display/tegra/
H A Dnvidia,tegra20-dc.yaml68 memory-region: true
95 - description: window A memory client
96 - description: window B memory client
98 - description: window C memory client
99 - description: cursor memory client
141 - description: window A memory client
142 - description: window B memory client
143 - description: window C memory client
144 - description: cursor memory client
145 - description: window D memory client
[all …]
/openbmc/u-boot/doc/device-tree-bindings/clock/
H A Drockchip,rk3368-dmc.txt1 RK3368 dynamic memory controller driver
4 The RK3368 DMC (dynamic memory controller) driver supports setup/initialisation
7 (a) a target-frequency (i.e. operating point) for the memory operation
9 (c) a memory-schedule (i.e. mapping from physical addresses to the address
10 pins of the memory bus)
44 - rockchip,memory-schedule:
54 #include <dt-bindings/memory/rk3368-dmc.h>
66 rockchip,memory-schedule = <DMC_MSCH_CBRD>;
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-firmware-efi-runtime-map5 that all efi memory ranges which have the runtime attribute
17 subdirectories are named with the number of the memory range::
28 attribute The attributes of the memory range.
29 num_pages The size of the memory range in pages.
30 phys_addr The physical address of the memory range.
31 type The type of the memory range.
32 virt_addr The virtual address of the memory range.
/openbmc/linux/Documentation/devicetree/bindings/remoteproc/
H A Drenesas,rcar-rproc.yaml28 memory-region:
30 List of phandles to the reserved memory regions associated with the
34 (see ../reserved-memory/reserved-memory.yaml)
39 - memory-region
48 reserved-memory {
60 memory-region = <&cr7_ram>;
/openbmc/linux/arch/arm64/boot/dts/qcom/
H A Dsc7280-chrome-common.dtsi5 * This file mainly tries to abstract out the memory protections put into
14 * Reserved memory changes
16 * Delete all unused memory nodes and define the peripheral memory regions
26 reserved-memory {
27 adsp_mem: memory@86700000 {
32 camera_mem: memory@8ad00000 {
37 venus_mem: memory@8b200000 {
42 wpss_mem: memory@9ae00000 {
103 /* TF-A firmware maps memory cached so mark dma-coherent to match. */
/openbmc/linux/Documentation/devicetree/bindings/soc/fsl/
H A Dqman.txt63 - memory-regions
66 Definition: List of phandles referencing the QMan private memory
83 This memory is reserved/allocated as a node under the /reserved-memory node.
85 For additional details about reserved memory regions see reserved-memory.txt
87 The QMan FQD memory node must be named "qman-fqd"
98 The QMan PFDR memory node must be named "qman-pfdr"
109 The following constraints are relevant to the FQD and PFDR private memory:
112 - The alignment must be a muliptle of the memory size
120 For additional details about reserved memory regions see reserved-memory.txt
126 reserved-memory {
[all …]
/openbmc/linux/Documentation/core-api/
H A Dgenalloc.rst4 There are a number of memory-allocation subsystems in the kernel, each
6 implement a new allocator for a specific range of special-purpose memory;
7 often that memory is located on a device somewhere. The author of the
12 for the creation of ad hoc memory allocators. This code was merged
30 multiple of eight bytes. Increasing min_alloc_order decreases the memory
31 required to track the memory in the pool. The nid parameter specifies
58 A call to gen_pool_add() will place the size bytes of memory
79 memory for use with DMA operations, returning the associated physical
87 how the allocation functions choose which specific piece of memory to
117 If the indicated memory is not available the allocation fails.
[all …]
/openbmc/linux/drivers/gpu/drm/nouveau/nvkm/engine/fifo/
H A Dgv100.c119 const u64 bar2 = cctx ? nvkm_memory_bar2(cctx->vctx->inst->memory) : 0ULL; in gv100_ectx_ce_bind()
131 if (nvkm_memory_bar2(vctx->inst->memory) == ~0ULL) in gv100_ectx_ce_ctor()
183 gv100_runl_insert_chan(struct nvkm_chan *chan, struct nvkm_memory *memory, u64 offset) in gv100_runl_insert_chan() argument
188 nvkm_wo32(memory, offset + 0x0, lower_32_bits(user) | chan->runq << 1); in gv100_runl_insert_chan()
189 nvkm_wo32(memory, offset + 0x4, upper_32_bits(user)); in gv100_runl_insert_chan()
190 nvkm_wo32(memory, offset + 0x8, lower_32_bits(inst) | chan->id); in gv100_runl_insert_chan()
191 nvkm_wo32(memory, offset + 0xc, upper_32_bits(inst)); in gv100_runl_insert_chan()
197 nvkm_wo32(memory, offset + 0x0, (128 << 24) | (3 << 16) | 0x00000001); in gv100_runl_insert_cgrp()
198 nvkm_wo32(memory, offset + 0x4, cgrp->chan_nr); in gv100_runl_insert_cgrp()
199 nvkm_wo32(memory, offset + 0x8, cgrp->id); in gv100_runl_insert_cgrp()
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/PersistentMemory/
H A DPartition.interface.yaml2 Implement to provide memory partition attributes.
11 Size of this memory region in kibibytes (KiB).
15 Classification of memory occupied by the given memory region.
20 memory region in KiB.
/openbmc/linux/Documentation/devicetree/bindings/media/
H A Daspeed-video.txt10 - reg: contains the offset and length of the VE memory region
19 - memory-region:
20 phandle to a memory region to allocate from, as defined in
21 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
32 memory-region = <&video_engine_memory>;
H A Dmediatek-vpu.txt17 - memory-region: phandle to a node describing memory (see
18 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt)
19 to be used for VPU extended memory; if not present, VPU may be located
20 anywhere in the memory
/openbmc/linux/tools/memory-model/
H A DREADME9 This directory contains the memory consistency model (memory model, for
46 memory model maintainers.
73 tools/memory-model/litmus-tests/
85 tools/memory-model/Documentation/litmus-tests.txt
88 located in the tools/memory-model directory.
90 To run SB+fencembonceonces.litmus against the memory model:
92 $ cd $LINUX_SOURCE_TREE/tools/memory-model
169 Categorizes the relevant instructions, including memory
174 event types used by the memory model and (2) performs RCU
182 by the memory model. Allowed executions are those which
[all …]
/openbmc/qemu/docs/system/devices/
H A Dvirtio-pmem.rst7 The virtio pmem device is a paravirtualized persistent memory device
14 host page cache. This reduces guest memory footprint as the host can
15 make efficient memory reclaim decisions under memory pressure.
28 A virtio pmem device backed by a memory-backend-file can be created on
31 -object memory-backend-file,id=mem1,share,mem-path=./virtio_pmem.img,size=4G
36 - "object memory-backend-file,id=mem1,share,mem-path=<image>, size=<image size>"
40 pci device whose storage is provided by above memory backend device.
49 memory backing has to be added via 'object_add'; afterwards, the virtio
55 (qemu) object_add memory-backend-file,id=mem2,share=on,mem-path=virtio_pmem2.img,size=4G
H A Dcxl.rst4 targets accelerators and memory devices attached to a CXL host.
27 - BAR mapped memory accesses used for registers and mailboxes.
37 supported by the host for normal memory should also work for
38 CXL attached memory devices.
51 via means such as PCI memory reads and writes to BARs.
89 memory devices. It is provide as CFMW Structures (CFMWS) in
135 the HDM decoders which route incoming memory accesses to the
232 RP 1 and hence to yet more regions of the memory of the
318 -object memory-backend-ram,id=vmem0,share=on,size=256M \
328 -object memory-backend-ram,id=vmem0,share=on,size=256M \
[all …]
/openbmc/linux/tools/testing/selftests/mm/
H A Dhugetlb_reparenting_test.sh25 CGROUP_ROOT=/dev/cgroup/memory
33 CGROUP_ROOT=/dev/cgroup/memory
34 mount -t cgroup memory,hugetlb $CGROUP_ROOT
205 echo Assert memory charged correctly for parent use.
210 echo Assert memory charged correctly for child use.
215 echo Assert memory reparent correctly.
220 echo Assert memory uncharged correctly.
235 echo Assert memory charged correctly for child only use.
239 echo Assert memory reparent correctly.
244 echo Assert memory uncharged correctly.
/openbmc/linux/Documentation/devicetree/bindings/memory-controllers/
H A Darm,pl35x-smc.yaml4 $id: http://devicetree.org/schemas/memory-controllers/arm,pl35x-smc.yaml#
14 of memory interfaces, which are NAND and memory mapped interfaces (such as
33 pattern: "^memory-controller@[0-9a-f]+$"
78 bus. The controller can be a NAND controller or a pair of any memory
84 Compatible of memory controller.
94 Offset of the memory region requested by the device.
96 Length of the memory region requested by the device.
129 - description: clock for the memory device bus
139 smcc: memory-controller@e000e000 {
/openbmc/linux/drivers/memory/tegra/
H A DKconfig23 This driver is required to change memory timings / clock rate for
24 external memory.
35 This driver is required to change memory timings / clock rate for
36 external memory.
47 This driver is required to change memory timings / clock rate for
48 external memory.
61 This driver is required to change memory timings / clock rate for
62 external memory.
/openbmc/linux/Documentation/devicetree/bindings/reserved-memory/
H A Dqcom,cmd-db.yaml4 $id: http://devicetree.org/schemas/reserved-memory/qcom,cmd-db.yaml#
12 is stored in a shared memory region and is loaded by the remote processor.
17 remote processor and made available in the shared memory.
23 - $ref: reserved-memory.yaml
36 reserved-memory {
41 reserved-memory@85fe0000 {
H A Dqcom,rmtfs-mem.yaml4 $id: http://devicetree.org/schemas/reserved-memory/qcom,rmtfs-mem.yaml#
10 This binding describes the Qualcomm remote filesystem memory, which serves the
11 purpose of describing the shared memory region used for remote processors to
18 - $ref: reserved-memory.yaml
32 Array of vmids of the remote processors, to set up memory protection
43 reserved-memory {
/openbmc/linux/arch/arm64/boot/dts/ti/
H A Dk3-j7200-som-p0.dtsi11 memory@80000000 {
12 device_type = "memory";
18 reserved_memory: reserved-memory {
35 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 {
47 mcu_r5fss0_core1_memory_region: r5f-memory@a1100000 {
59 main_r5fss0_core0_memory_region: r5f-memory@a2100000 {
71 main_r5fss0_core1_memory_region: r5f-memory@a3100000 {
218 memory-region = <&mcu_r5fss0_core0_dma_memory_region>,
224 memory-region = <&mcu_r5fss0_core1_dma_memory_region>,
230 memory-region = <&main_r5fss0_core0_dma_memory_region>,
[all …]
/openbmc/linux/drivers/xen/
H A DKconfig6 bool "Xen memory balloon driver"
11 return unneeded memory to the system.
24 memory ranges to use in order to map foreign memory or grants.
33 where <maxmem> is >= requested memory size,
36 where <memory> is requested memory size; alternatively memory
46 for i in /sys/devices/system/memory/memory*/state; do \
54 int "Hotplugged memory limit (in GiB) for a PV guest"
60 expanded to when using memory hotplug.
62 A PV guest can have more memory than this limit if is
66 tables needed for physical memory administration.
[all …]

12345678910>>...214