| /openbmc/linux/Documentation/devicetree/bindings/memory-controllers/ |
| H A D | nuvoton,npcm-memory-controller.yaml | 4 $id: http://devicetree.org/schemas/memory-controllers/nuvoton,npcm-memory-controller.yaml#
14 The Nuvoton BMC SoC supports DDR4 memory with or without ECC (error correction
17 The memory controller supports single bit error correction, double bit error
18 detection (in-line ECC in which a section (1/8th) of the memory device used to
21 Note, the bootloader must configure ECC mode for the memory controller.
26 - nuvoton,npcm750-memory-controller
27 - nuvoton,npcm845-memory-controller
46 mc: memory-controller@f0824000 {
47 compatible = "nuvoton,npcm750-memory-controller";
|
| /openbmc/linux/drivers/gpu/drm/nouveau/nvkm/subdev/instmem/ |
| H A D | nv04.c | 48 struct nv04_instobj *iobj = nv04_instobj(memory); in nv04_instobj_wr32()
68 nv04_instobj_release(struct nvkm_memory *memory) in nv04_instobj_release() argument
73 nv04_instobj_acquire(struct nvkm_memory *memory) in nv04_instobj_acquire() argument
81 nv04_instobj_size(struct nvkm_memory *memory) in nv04_instobj_size() argument
83 return nv04_instobj(memory)->node->length; in nv04_instobj_size()
87 nv04_instobj_addr(struct nvkm_memory *memory) in nv04_instobj_addr() argument
89 return nv04_instobj(memory)->node->offset; in nv04_instobj_addr()
93 nv04_instobj_target(struct nvkm_memory *memory) in nv04_instobj_target() argument
99 nv04_instobj_dtor(struct nvkm_memory *memory) in nv04_instobj_dtor() argument
129 *pmemory = &iobj->base.memory; in nv04_instobj_new()
[all …]
|
| H A D | gk20a.c | 52 struct nvkm_memory memory; member
116 gk20a_instobj_target(struct nvkm_memory *memory) in gk20a_instobj_target() argument
122 gk20a_instobj_page(struct nvkm_memory *memory) in gk20a_instobj_page() argument
128 gk20a_instobj_addr(struct nvkm_memory *memory) in gk20a_instobj_addr() argument
134 gk20a_instobj_size(struct nvkm_memory *memory) in gk20a_instobj_size() argument
191 const u64 size = nvkm_memory_size(memory); in gk20a_instobj_acquire_iommu()
286 .memory = &node->memory, in gk20a_instobj_map()
295 gk20a_instobj_dtor_dma(struct nvkm_memory *memory) in gk20a_instobj_dtor_dma() argument
395 node->base.memory.ptrs = &gk20a_instobj_ptrs; in gk20a_instobj_ctor_dma()
442 node->base.memory.ptrs = &gk20a_instobj_ptrs; in gk20a_instobj_ctor_iommu()
[all …]
|
| H A D | nv40.c | 50 struct nv40_instobj *iobj = nv40_instobj(memory); in nv40_instobj_wr32()
68 nv40_instobj_release(struct nvkm_memory *memory) in nv40_instobj_release() argument
74 nv40_instobj_acquire(struct nvkm_memory *memory) in nv40_instobj_acquire() argument
81 nv40_instobj_size(struct nvkm_memory *memory) in nv40_instobj_size() argument
83 return nv40_instobj(memory)->node->length; in nv40_instobj_size()
87 nv40_instobj_addr(struct nvkm_memory *memory) in nv40_instobj_addr() argument
89 return nv40_instobj(memory)->node->offset; in nv40_instobj_addr()
93 nv40_instobj_target(struct nvkm_memory *memory) in nv40_instobj_target() argument
99 nv40_instobj_dtor(struct nvkm_memory *memory) in nv40_instobj_dtor() argument
129 *pmemory = &iobj->base.memory; in nv40_instobj_new()
[all …]
|
| /openbmc/linux/Documentation/mm/ |
| H A D | numa.rst | 12 or more CPUs, local memory, and/or IO buses. For brevity and to
32 cell containing the target memory. For example, access to memory by CPUs
39 memory bandwidth. However, to achieve scalable memory bandwidth, system and
41 [cache misses] to be to "local" memory--memory on the same cell, if any--or
42 to the closest cell with memory.
50 CPUs, memory and/or IO buses. And, again, memory accesses to memory on
70 For each node with memory, Linux constructs an independent memory management
110 allocation behavior using Linux NUMA memory policy. [see
125 does contain memory overflows.
130 a subsystem allocates per CPU memory resources, for example.
[all …]
|
| H A D | hmm.rst | 6 memory like GPU on board memory) into regular kernel path, with the cornerstone
34 driver and regular application memory (private anonymous, shared memory, or
60 various memory copies.
77 buses only allow basic memory access from device to main memory; even cache
85 memory and cannot perform atomic operations on it. Thus device memory cannot
100 access any memory but we must also permit any memory to be migrated to device
128 memory for the device memory and second to perform migration. Policy decisions
316 system memory and device private memory.
433 back from device memory to regular memory cannot fail because it would
435 get more experience in how device memory is used and its impact on memory
[all …]
|
| /openbmc/linux/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/ |
| H A D | umem.c | 38 struct nvkm_memory *memory = NULL; in nvkm_umem_search() local
48 memory = nvkm_memory_ref(umem->memory); in nvkm_umem_search()
56 memory = nvkm_memory_ref(umem->memory); in nvkm_umem_search()
59 return memory ? memory : ERR_PTR(-ENOENT); in nvkm_umem_search()
98 int ret = nvkm_mem_map_host(umem->memory, &umem->map); in nvkm_umem_map()
103 *length = nvkm_memory_size(umem->memory); in nvkm_umem_map()
130 nvkm_memory_unref(&umem->memory); in nvkm_umem_dtor()
178 &umem->memory); in nvkm_umem_new()
186 args->v0.page = nvkm_memory_page(umem->memory); in nvkm_umem_new()
187 args->v0.addr = nvkm_memory_addr(umem->memory); in nvkm_umem_new()
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/reserved-memory/ |
| H A D | reserved-memory.yaml | 4 $id: http://devicetree.org/schemas/reserved-memory/reserved-memory.yaml#
7 title: /reserved-memory Child Node Common
13 Reserved memory is specified as a node under the /reserved-memory node. The
16 memory regions. Such memory regions are usually designed for the special
19 Each child of the reserved-memory node specifies one or more regions
23 memory.
52 Address and Length pairs. Specifies regions of memory that are
144 reserved-memory {
153 * the ADSP for I/O memory and private memory allocations.
172 memory-region = <&adsp_resv>;
[all …]
|
| H A D | memory-region.yaml | 4 $id: http://devicetree.org/schemas/reserved-memory/memory-region.yaml#
13 Regions in the /reserved-memory node may be referenced by other device
14 nodes by adding a memory-region property to the device node.
19 memory-region:
22 Phandle to a /reserved-memory child node assigned to the device.
24 memory-region-names:
28 memory-region property
37 memory-region = <&display_reserved>;
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-mm-memory-tiers | 3 Contact: Linux memory management mailing list <linux-mm@kvack.org>
4 Description: A collection of all the memory tiers allocated.
6 Individual memory tier details are contained in subdirectories
7 named by the abstract distance of the memory tier.
15 Contact: Linux memory management mailing list <linux-mm@kvack.org>
16 Description: Directory with details of a specific memory tier
19 memory tier, memtierN, where N is derived based on abstract distance.
21 A smaller value of N implies a higher (faster) memory tier in the
24 nodelist: NUMA nodes that are part of this memory tier.
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | firmware-assisted-dump.rst | 50 low memory regions (boot memory) from source to destination area.
54 The term 'boot memory' means size of the low memory chunk
56 booted with restricted memory. By default, the boot memory
68 - After the low memory (boot memory) area has been saved, the
78 boot memory size effectively booting with restricted memory
90 memory back to general use, except the memory required for
134 memory is held.
151 kernel memory and most of the user space memory except the user pages
156 Low memory Top of memory
185 Low memory Top of memory
[all …]
|
| /openbmc/linux/arch/arm64/boot/dts/ti/ |
| H A D | k3-j721e-som-p0.dtsi | 13 memory@80000000 {
14 device_type = "memory";
20 reserved_memory: reserved-memory {
37 mcu_r5fss0_core0_memory_region: r5f-memory@a0100000 {
103 c66_1_dma_memory_region: c66-dma-memory@a6000000 {
109 c66_0_memory_region: c66-memory@a6100000 {
121 c66_1_memory_region: c66-memory@a7100000 {
133 c71_0_memory_region: c71-memory@a8100000 {
430 memory-region = <&c66_0_dma_memory_region>,
437 memory-region = <&c66_1_dma_memory_region>,
[all …]
|
| /openbmc/qemu/tests/tcg/arm/ |
| H A D | Makefile.softmmu-target | 45 memory: CFLAGS+=-DCHECK_UNALIGNED=0
61 .PHONY: memory-record
62 run-memory-record: memory-record memory
67 $(QEMU_OPTS) memory)
69 .PHONY: memory-replay
70 run-memory-replay: memory-replay run-memory-record
75 $(QEMU_OPTS) memory)
77 EXTRA_RUNS+=run-memory-replay
|
| /openbmc/linux/drivers/dax/ |
| H A D | Kconfig | 3 tristate "DAX: direct access to differentiated memory"
13 latency...) memory via an mmap(2) capable character
15 platform memory resource that is differentiated from the
16 baseline memory pool. Mappings of a /dev/daxX.Y device impose
20 tristate "PMEM DAX: direct access to persistent memory"
24 Support raw access to persistent memory. Note that this
25 driver consumes memory ranges allocated and exported by the
37 memory. For example, a high bandwidth memory pool. The
39 memory from typical usage by default. This driver creates
40 device-dax instances for these memory ranges, and that also
[all …]
|
| /openbmc/linux/tools/testing/memblock/tests/ |
| H A D | basic_api.c | 18 ASSERT_EQ(memblock.memory.cnt, 1); in memblock_initialization_check()
45 rgn = &memblock.memory.regions[0]; in memblock_add_simple_check()
60 ASSERT_EQ(memblock.memory.cnt, 1); in memblock_add_simple_check()
78 rgn = &memblock.memory.regions[0]; in memblock_add_node_simple_check()
97 ASSERT_EQ(memblock.memory.cnt, 1); in memblock_add_node_simple_check()
121 rgn1 = &memblock.memory.regions[0]; in memblock_add_disjoint_check()
122 rgn2 = &memblock.memory.regions[1]; in memblock_add_disjoint_check()
145 ASSERT_EQ(memblock.memory.cnt, 2); in memblock_add_disjoint_check()
175 rgn = &memblock.memory.regions[0]; in memblock_add_overlap_top_check()
197 ASSERT_EQ(memblock.memory.cnt, 1); in memblock_add_overlap_top_check()
[all …]
|
| /openbmc/linux/Documentation/admin-guide/mm/damon/ |
| H A D | reclaim.rst | 8 be used for proactive and lightweight reclamation under light memory pressure.
15 On general memory over-committed systems, proactively reclaiming cold pages
22 memory to host, and the host reallocates the reported memory to other guests.
23 As a result, the memory of the systems are fully utilized. However, the
36 out memory regions that didn't accessed longer time first. System
99 Limit of size of memory for the reclamation in bytes.
129 Free memory rate (per thousand) for the high watermark.
138 Free memory rate (per thousand) for the middle watermark.
147 Free memory rate (per thousand) for the low watermark.
193 Start of target memory region in physical address.
[all …]
|
| H A D | lru_sort.rst | 33 memory regions that showing no access for a time that longer than a
135 Free memory rate (per thousand) for the high watermark.
144 Free memory rate (per thousand) for the middle watermark.
153 Free memory rate (per thousand) for the low watermark.
201 Start of target memory region in physical address.
209 End of target memory region in physical address.
225 Number of hot memory regions that tried to be LRU-sorted.
230 Total bytes of hot memory regions that tried to be LRU-sorted.
235 Number of hot memory regions that successfully be LRU-sorted.
250 Number of cold memory regions that tried to be LRU-sorted.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/pmem/ |
| H A D | pmem-region.txt | 1 Device-tree bindings for persistent memory regions
4 Persistent memory refers to a class of memory devices that are:
6 a) Usable as main system memory (i.e. cacheable), and
9 Given b) it is best to think of persistent memory as a kind of memory mapped
11 persistent regions separately to the normal memory pool. To aid with that this
13 memory regions exist inside the physical address space.
24 range should be mappable as normal system memory would be
36 backed by non-persistent memory. This lets the OS know that it
41 is backed by non-volatile memory.
48 * 0x5000 to 0x5fff that is backed by non-volatile memory.
[all …]
|
| /openbmc/linux/arch/arm64/boot/dts/renesas/ |
| H A D | r8a77951-salvator-x.dts | 16 memory@48000000 {
17 device_type = "memory";
22 memory@500000000 {
23 device_type = "memory";
27 memory@600000000 {
28 device_type = "memory";
32 memory@700000000 {
33 device_type = "memory";
|
| H A D | r8a77951-ulcb.dts | 17 memory@48000000 {
18 device_type = "memory";
23 memory@500000000 {
24 device_type = "memory";
28 memory@600000000 {
29 device_type = "memory";
33 memory@700000000 {
34 device_type = "memory";
|
| H A D | r8a77951-salvator-xs.dts | 16 memory@48000000 {
17 device_type = "memory";
22 memory@500000000 {
23 device_type = "memory";
27 memory@600000000 {
28 device_type = "memory";
32 memory@700000000 {
33 device_type = "memory";
|
| H A D | r8a779m1-salvator-xs.dts | 20 memory@48000000 {
21 device_type = "memory";
26 memory@500000000 {
27 device_type = "memory";
31 memory@600000000 {
32 device_type = "memory";
36 memory@700000000 {
37 device_type = "memory";
|
| H A D | r8a779m1-ulcb.dts | 21 memory@48000000 {
22 device_type = "memory";
27 memory@500000000 {
28 device_type = "memory";
32 memory@600000000 {
33 device_type = "memory";
37 memory@700000000 {
38 device_type = "memory";
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | r8a7795-h3ulcb.dts | 17 memory@48000000 {
18 device_type = "memory";
23 memory@500000000 {
24 device_type = "memory";
28 memory@600000000 {
29 device_type = "memory";
33 memory@700000000 {
34 device_type = "memory";
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | ivshmem.rst | 4 On Linux hosts, a shared memory device is available. The basic syntax
11 where hostmem names a host memory backend. For a POSIX shared memory
16 -object memory-backend-file,size=1M,share,mem-path=/dev/shm/ivshmem,id=hostmem
19 shared memory region. Interrupt support requires using a shared memory
21 shared memory server is qemu.git/contrib/ivshmem-server. An example
22 syntax when using the shared memory server is:
42 memory on migration to the destination host. With ``master=off``, the
47 At most one of the devices sharing the same memory can be master. The
54 memory backend that has hugepage support:
58 …|qemu_system_x86| -object memory-backend-file,size=1G,mem-path=/dev/hugepages/my-shmem-file,share,…
[all …]
|