| /openbmc/docs/designs/ |
| H A D | ecc-dbus-sel.md | 9 The IPMI SELs only define memory Error Correction Code (ECC) errors for host
10 memory rather than BMC.
18 The IPMI specification defines memory system event log about ECC/other
21 format and creates BMC memory ECC event log.
26 memory ECC SEL as well.
41 ECC-enabled memory controllers can detect and correct errors in operating
44 they become catastrophic faulty memory module.
46 Many ECC memory systems use an "external" EDAC between the CPU and the memory to
47 fix memory error. Most host integrate EDAC into the CPU's integrated memory
80 - object path : `/xyz/openbmc_project/metrics/memory/BmcECC`
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/iommu/ |
| H A D | mediatek,iommu.yaml | 129 dt-binding/memory/mediatek,mt8188-memory-port.h for mt8188,
131 dt-binding/memory/mt2712-larb-port.h for mt2712,
132 dt-binding/memory/mt6779-larb-port.h for mt6779,
133 dt-binding/memory/mt6795-larb-port.h for mt6795,
134 dt-binding/memory/mt8167-larb-port.h for mt8167,
135 dt-binding/memory/mt8173-larb-port.h for mt8173,
136 dt-binding/memory/mt8183-larb-port.h for mt8183,
137 dt-binding/memory/mt8186-memory-port.h for mt8186,
138 dt-binding/memory/mt8192-larb-port.h for mt8192.
139 dt-binding/memory/mt8195-memory-port.h for mt8195.
[all …]
|
| /openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | memcg_test.rst | 22 Allocated at boot or memory hotplug. Freed at memory hot removal.
203 memory hotplug test is one of good test.
205 to offline memory, do following::
209 (XXX is the place of memory)
256 # mount -t cgroup none /cgroup -o memory
258 # echo 40M > /cgroup/test/memory.limit_in_bytes
287 #echo 50M > /memory.limit_in_bytes
293 #echo 50M > memory.limit_in_bytes
294 #echo 50M > memory.memsw.limit_in_bytes
313 #echo 1 >/cgroup/B/memory.move_charge_at_immigrate
[all …]
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | edac.rst | 18 The individual DRAM chips on a memory stick. These devices commonly
20 provides the number of bits that the memory controller expects:
25 A printed circuit board that aggregates multiple memory devices in
32 A physical connector on the motherboard that accepts a single memory
77 A Single-ranked stick has 1 chip-select row of memory. Motherboards
93 of memory devices. The two rows cannot be accessed concurrently.
95 both sides of the memory stick.
99 All of the memory sticks that are required for a single memory access or
111 HBM is a new memory type with low power consumption and ultra-wide
173 mc/ <existing memory device directory>
[all …]
|
| /openbmc/linux/mm/ |
| H A D | Kconfig | 348 memory vulnerabilities.
519 # Don't discard allocated memory used to track "memory" and "reserved" memblocks
576 memory blocks in 'offline' state.
579 bool "Allow for memory hot remove"
617 # support for memory balloon
622 # support for memory balloon compaction
637 # support for memory compaction
639 bool "Allow for memory compaction"
956 bool "Track memory changes"
1075 bool "Unaddressable device memory (GPU memory, ...)"
[all …]
|
| /openbmc/linux/Documentation/PCI/endpoint/function/binding/ |
| H A D | pci-ntb.rst | 32 mw1 size of memory window1
33 mw2 size of memory window2
34 mw3 size of memory window3
35 mw4 size of memory window4
36 num_mws Number of memory windows; max = 4
|
| /openbmc/linux/Documentation/devicetree/bindings/reserved-memory/ |
| H A D | phram.yaml | 4 $id: http://devicetree.org/schemas/reserved-memory/phram.yaml#
10 Specifies that the reserved memory region can be used as an MTD or block
20 - $ref: reserved-memory.yaml
28 description: region of memory that can be used as an MTD/block device
38 reserved-memory {
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools/core/ |
| H A D | 0001-memory.h-Always-define-strlcpy-for-glibc-based-syste.patch | 4 Subject: [PATCH] memory.h: Always define strlcpy for glibc based systems
17 include/cutils/memory.h | 2 +-
20 diff --git a/include/cutils/memory.h b/include/cutils/memory.h
22 --- a/include/cutils/memory.h
23 +++ b/include/cutils/memory.h
|
| /openbmc/linux/Documentation/devicetree/bindings/media/ |
| H A D | amphion,vpu.yaml | 81 memory-region:
83 Phandle to the reserved memory nodes to be associated with the
84 remoteproc device. The reserved memory nodes should be carveout nodes,
86 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
89 - description: region used for RPC shared memory between firmware and
98 - memory-region
154 memory-region = <&decoder_boot>, <&decoder_rpc>;
165 memory-region = <&encoder1_boot>, <&encoder1_rpc>;
176 memory-region = <&encoder2_boot>, <&encoder2_rpc>;
|
| /openbmc/linux/Documentation/arch/x86/x86_64/ |
| H A D | fake-numa-for-cpusets.rst | 12 in conjunction with cpusets for coarse memory management. Using this feature,
13 you can create fake NUMA nodes that represent contiguous chunks of memory and
15 amount of system memory that are available to a certain class of tasks.
24 emulation setup of "numa=fake=4*512,". This will split our system memory into
43 Documentation/admin-guide/cgroup-v1/cpusets.rst, you can assign fake nodes (i.e. contiguous memory
54 memory allocations (1G).
56 You can now assign tasks to these cpusets to limit the memory resources
63 Notice the difference between the system memory usage as reported by
75 This allows for coarse memory management for the tasks you assign to particular
78 memory management needs.
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | unaligned-memory-access.rst | 14 when it comes to memory access. This document presents some details about
25 reading 4 bytes of data from address 0x10005 would be an unaligned memory
30 or write a number of bytes to or from memory (e.g. movb, movw, movl in x86
40 When accessing N bytes of memory, the base memory address must be evenly
47 of memory access. However, we must consider ALL supported architectures;
59 - Some architectures are able to perform unaligned memory accesses
72 memory accesses to happen, your code will not work correctly on certain
81 memory addresses of certain variables, etc.
117 resident memory size of structure instances. The optimal layout of the
170 2 bytes (16 bits) to be read from memory starting at address addr1.
[all …]
|
| H A D | boot-time-mm.rst | 2 Boot time memory management
5 Early system initialization cannot use "normal" memory management
7 allocate memory for various data structures, for instance for the
11 boot time memory management. The architecture specific initialization
15 Once the early memory management is available it offers a variety of
16 functions and macros for memory allocations. The allocation request
|
| /openbmc/linux/Documentation/arch/ia64/ |
| H A D | aliasing.rst | 13 Itanium supports several attributes for virtual memory references.
40 Platform firmware describes the physical memory map and the
57 memory described by the efi_memmap. Linux/ia64 can't use all memory
89 homogeneous with respect to memory attributes.
106 an attribute reported as being supported in the EFI memory map.
108 Since the EFI memory map does not describe MMIO on some
162 If the EFI memory map reports that the entire granule supports
166 If the granule contains non-WB memory, but we can cover the
178 The EFI memory map may not report these MMIO regions.
188 The EFI memory map reports the following attributes:
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-edac | 5 counters for UE and CE errors on the given memory controller.
29 that this memory controller manages.
35 errors that have occurred on this memory controller. If
43 occurred on this memory controller with no information as to
50 errors that have occurred on this memory controller. This
60 have occurred on this memory controller wherewith no
63 to indicate which slot the failing memory is in. This count
70 The scrubbing rate used by the memory controller is set by
83 available memory slot in this memory controller. It is used by
91 For dimm*/size, this is the size, in MB of the DIMM memory
[all …]
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | sysfs-devices-node | 17 Nodes that have regular memory.
29 Nodes that have regular or high memory.
77 The node's zoned virtual memory statistics.
105 The directory containing symlinks to memory initiator
107 memory. CPUs and other memory initiators in nodes not in
108 the list accessing this node's memory may have different
115 The directory containing symlinks to memory targets that
171 The size of this memory side cache in bytes.
184 The total amount of SGX physical memory in bytes.
191 corrupted data due to memory errors) on a NUMA node.
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | userp.rst | 14 particular user pointer method (not only memory mapping) is supported
16 with the memory type set to ``V4L2_MEMORY_USERPTR``.
18 This I/O method combines advantages of the read/write and memory mapping
20 can reside for example in virtual or shared memory. Only pointers to
39 reqbuf.memory = V4L2_MEMORY_USERPTR;
54 driver swaps memory pages within physical memory to create a continuous
56 virtual memory subsystem of the kernel. When buffer pages have been
58 memory for DMA. [#f1]_
62 memory pages at any time between the completion of the DMA and this
63 ioctl. The memory is also unlocked when
[all …]
|
| /openbmc/linux/Documentation/riscv/ |
| H A D | vm-layout.rst | 10 This document describes the virtual memory layout used by the RISC-V Linux
39 …0000000000000000 | 0 | 0000003fffffffff | 256 GB | user-space virtual memory, different …
43 … | | | | virtual memory addresses up to the -256 GB
47 … | Kernel-space virtual memory, shared between all processes:
54 … ffffffd800000000 | -160 GB | fffffff6ffffffff | 124 GB | direct mapping of all physical memory
75 …0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory, different …
79 … | | | | virtual memory addresses up to the -128 TB
90 … ffffaf8000000000 | -80.5 TB | ffffef7fffffffff | 64 TB | direct mapping of all physical memory
111 …0000000000000000 | 0 | 00ffffffffffffff | 64 PB | user-space virtual memory, different …
115 … | | | | virtual memory addresses up to the -64 PB
[all …]
|
| /openbmc/linux/drivers/gpu/drm/nouveau/nvkm/engine/fifo/ |
| H A D | nv50.c | 241 u64 addr = nvkm_memory_addr(memory) + start; in nv50_runl_commit()
250 nvkm_wo32(memory, offset, chan->id); in nv50_runl_insert_chan()
287 struct nvkm_memory *memory; in nv50_runl_update() local
295 memory = nv50_runl_alloc(runl, &start); in nv50_runl_update()
296 if (IS_ERR(memory)) in nv50_runl_update()
297 return PTR_ERR(memory); in nv50_runl_update()
302 nvkm_kmap(memory); in nv50_runl_update()
306 runl->func->insert_cgrp(cgrp, memory, offset); in nv50_runl_update()
312 runl->func->insert_chan(chan, memory, offset); in nv50_runl_update()
316 nvkm_done(memory); in nv50_runl_update()
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/gpu/ |
| H A D | aspeed-gfx.txt | 19 - memory-region:
20 Phandle to a memory region to allocate from, as defined in
21 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
33 memory-region = <&gfx_memory>;
|
| /openbmc/u-boot/doc/usage/ |
| H A D | measured_boot.rst | 8 component's measurement in memory for the operating system to consume.
16 * Device-tree configuration of the TPM device to specify the memory area
18 a reserved memory region or "linux,sml-base" and "linux,sml-size"
19 indicating the address and size of the memory region. An example can be
21 * The operating system must also be configured to use the memory regions
|
| /openbmc/linux/Documentation/devicetree/bindings/mips/brcm/ |
| H A D | soc.txt | 43 A Broadcom STB SoC typically has a number of independent memory controllers,
46 describing these controllers as a parent "memory controllers" block, which
52 Represents a single memory controller instance.
58 the entire memory controller (including all sub nodes: DDR PHY,
65 memory-controller@0 {
88 Control registers for this memory controller's DDR PHY.
104 == DDR memory controller sequencer
106 Control registers for this memory controller's DDR memory sequencer
126 The memory controller arbiter is responsible for memory clients allocation
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | ras.rst | 102 Typically, it is very complex for memory, as modern CPUs interlace memory
150 Such kind of memory is called Error-correcting code memory (ECC memory).
156 ECC memory
169 on the memory modules.
193 .. [#f2] Some memory controllers also allow using memory in mirror mode. argument
198 memory modules (or 4 memory modules, if the system is also on Lock-step
332 used to refer to a memory module, although there are other memory
342 a given motherboard, memory controller and memory module characteristics.
368 for memory DIMMs:
548 memory controller identifies the location of a memory module.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/dsp/ |
| H A D | fsl,dsp.yaml | 69 memory-region:
71 phandle to a node describing reserved memory (System RAM memory)
72 used by DSP (see bindings/reserved-memory/reserved-memory.txt)
93 - memory-region
125 memory-region:
136 memory-region:
166 memory-region = <&dsp_reserved>;
202 memory-region = <&dsp_vdev0buffer>, <&dsp_vdev0vring0>,
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | ptdump.rst | 7 virtual memory layout as well as the attributes associated with the
9 kernel page tables to verify permissions and memory types. Examining the
12 improper memory protections.
15 memory without requiring a system reboot. To maintain the consistency
16 and integrity of the memory management data structures, arm64 makes use
20 offlining of memory being accessed by the ptdump code.
34 followed by size of the memory region covered by this entry, the
39 within the kernel memory. Assessing these attributes can assist in
40 understanding the memory layout, access patterns and security
43 Kernel virtual memory layout example::
|
| /openbmc/linux/Documentation/devicetree/bindings/pci/ |
| H A D | v3-v360epc-pci.txt | 17 - The non-prefetchable and prefetchable memory windows must
19 - The prefetchable memory window must be immediately adjacent
20 to the non-prefetcable memory window
21 - dma-ranges: three ranges for the inbound memory region. The ranges must
23 64MB, 128MB, 256MB, 512MB, 1GB or 2GB in size. The memory should be marked
45 0x02000000 0 0x40000000 /* non-prefectable memory @40000000 */
47 0x42000000 0 0x50000000 /* prefetchable memory @50000000 */
49 dma-ranges = <0x02000000 0 0x20000000 /* EBI memory space */
51 0x02000000 0 0x80000000 /* Core module alias memory */
|