| /openbmc/linux/Documentation/arch/x86/x86_64/ |
| H A D | mm.rst | 7 Complete virtual memory map with 4-level page tables
49 ffffea0000000000 | -22 TB | ffffeaffffffffff | 1 TB | virtual memory map (vmemmap_base)
51 ffffec0000000000 | -20 TB | fffffbffffffffff | 16 TB | KASAN shadow memory
75 Complete virtual memory map with 5-level page tables
80 - With 56-bit addresses, user-space memory gets expanded by a factor of 512x,
83 memory supported.
110 ffdf000000000000 | -8.25 PB | fffffbffffffffff | ~8 PB | KASAN shadow memory
139 The direct mapping covers all memory in the system up to the highest
140 memory address (this means in some cases it can also include PCI memory
144 memory window (this size is arbitrary, it can be raised later if needed).
[all …]
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | memory-allocation.rst | 7 Linux provides a variety of APIs for memory allocation. You can
14 Most of the memory allocation APIs use GFP flags to express how that
15 memory should be allocated. The GFP acronym stands for "get free
16 pages", the underlying memory allocation function.
19 makes the question "How should I allocate memory?" not that easy to
32 The GFP flags control the allocators behavior. They tell what memory
34 memory, whether the memory can be accessed by the userspace etc. The
131 Selecting memory allocator
136 routines that set memory to zero, like kzalloc(). If you need to
171 wrappers can allocate memory from that cache.
[all …]
|
| /openbmc/linux/arch/arm64/boot/dts/renesas/ |
| H A D | r8a77961-ulcb.dts | 16 memory@48000000 {
17 device_type = "memory";
22 memory@480000000 {
23 device_type = "memory";
27 memory@600000000 {
28 device_type = "memory";
|
| H A D | r8a77961-salvator-xs.dts | 16 memory@48000000 {
17 device_type = "memory";
22 memory@480000000 {
23 device_type = "memory";
27 memory@600000000 {
28 device_type = "memory";
|
| H A D | r8a779m3-ulcb.dts | 19 memory@48000000 {
20 device_type = "memory";
25 memory@480000000 {
26 device_type = "memory";
30 memory@600000000 {
31 device_type = "memory";
|
| H A D | r8a779m3-salvator-xs.dts | 20 memory@48000000 {
21 device_type = "memory";
26 memory@480000000 {
27 device_type = "memory";
31 memory@600000000 {
32 device_type = "memory";
|
| /openbmc/linux/arch/arm/boot/dts/st/ |
| H A D | ste-db8500.dtsi | 15 reserved-memory {
20 /* Modem trace memory */
26 /* Modem shared memory */
32 /* Modem private memory */
39 * Initial Secure Software ISSW memory
45 * be too careful, so reserve this memory anyway.
|
| H A D | ste-db8520.dtsi | 15 reserved-memory {
20 /* Modem trace memory */
26 /* Modem shared memory */
32 /* Modem private memory */
39 * Initial Secure Software ISSW memory
45 * be too careful, so reserve this memory anyway.
|
| /openbmc/linux/Documentation/devicetree/bindings/ |
| H A D | numa.txt | 106 4 - Empty memory nodes
109 Empty memory nodes, which no memory resides in, are allowed. There are no
116 memory@0 {
117 device_type = "memory";
122 memory@80000000 {
123 device_type = "memory";
128 /* Empty memory node 2 and 3 */
156 memory@c00000 {
157 device_type = "memory";
163 memory@10000000000 {
[all …]
|
| /openbmc/qemu/qapi/ |
| H A D | machine.json | 678 # @memory: the structure represents the memory performance
732 # memory or side cache.
799 # Set the memory side cache information for a given memory domain.
804 # @node-id: the memory proximity domain to which the memory belongs.
901 # @dump: whether memory backend's memory is included in a core dump
915 # @policy: memory policy of memory backend
1287 # @base-memory: size of "base" memory specified with command line
1290 # @plugged-memory: size of memory that can be hot-unplugged. This
1297 'data' : { 'base-memory': 'size', '*plugged-memory': 'size' } }
1531 # @type: memory device type
[all …]
|
| /openbmc/linux/drivers/gpu/drm/amd/amdkfd/ |
| H A D | Kconfig | 16 bool "Enable HMM-based shared virtual memory manager"
22 Enable this to use unified memory and managed memory in HIP. This
23 memory manager supports two modes of operation. One based on
25 based memory management on most GFXv9 GPUs, set the module
35 in peer GPUs' memory without intermediate copies in system memory.
38 GPUs with large memory BARs that expose the entire VRAM in PCIe bus
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | ramoops.rst | 19 Ramoops uses a predefined memory area to store the dump. The start and size
20 and type of the memory area are set using three variables:
23 * ``mem_size`` for the size. The memory size will be rounded down to a
32 memory are implementation defined, and won't work on many ARMs such as omaps.
33 Setting ``mem_type=2`` attempts to treat the memory region as normal memory,
36 The memory area is divided into ``record_size`` chunks (also rounded down to
52 Ramoops also supports software ECC protection of persistent memory regions.
64 boot and then use the reserved memory for ramoops. For example, assuming a
72 ``Documentation/devicetree/bindings/reserved-memory/ramoops.yaml``.
75 reserved-memory {
[all …]
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | amd-memory-encryption.rst | 10 SME provides the ability to mark individual pages of memory as encrypted using
19 memory. Private memory is encrypted with the guest-specific key, while shared
38 memory. Since the memory encryption bit is controlled by the guest OS when it
40 forces the memory encryption bit to 1.
49 Bits[5:0] pagetable bit number used to activate memory
52 memory encryption is enabled (this only affects
57 determine if SME is enabled and/or to enable memory encryption::
60 Bit[23] 0 = memory encryption features are disabled
61 1 = memory encryption features are enabled
67 Bit[0] 0 = memory encryption is not active
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/reserved-memory/ |
| H A D | nvidia,tegra264-bpmp-shmem.yaml | 4 $id: http://devicetree.org/schemas/reserved-memory/nvidia,tegra264-bpmp-shmem.yaml#
7 title: Tegra CPU-NS - BPMP IPC reserved memory
13 Define a memory region used for communication between CPU-NS and BPMP.
16 The memory region is defined using a child node under /reserved-memory.
20 - $ref: reserved-memory.yaml
38 reserved-memory {
|
| H A D | shared-dma-pool.yaml | 4 $id: http://devicetree.org/schemas/reserved-memory/shared-dma-pool.yaml#
7 title: /reserved-memory DMA pool
13 - $ref: reserved-memory.yaml
20 This indicates a region of memory meant to be used as a shared
27 This indicates a region of memory meant to be used as a pool
28 of restricted DMA buffers for a set of devices. The memory
35 accessing the system memory at unexpected times and/or
40 leakage and system memory corruption, the system needs to
41 provide way to lock down the memory access, e.g., MPU. Note
51 the default pool of the contiguous memory allocator.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/memory-controllers/ |
| H A D | nvidia,tegra186-mc.yaml | 4 $id: http://devicetree.org/schemas/memory-controllers/nvidia,tegra186-mc.yaml#
14 The NVIDIA Tegra186 SoC features a 128 bit memory controller that is split
16 handles memory requests for 40-bit virtual addresses from internal clients
17 and arbitrates among them to allocate memory bandwidth.
19 Up to 15 GiB of physical memory can be supported. Security features such as
27 pattern: "^memory-controller@[0-9a-f]+$"
62 "^external-memory-controller@[0-9a-f]+$":
64 The bulk of the work involved in controlling the external memory
88 - description: external memory clock
242 memory-controller@2c00000 {
[all …]
|
| /openbmc/linux/drivers/char/agp/ |
| H A D | frontend.c | 273 agp_free_memory(memory); in agp_free_memory_wrap()
281 if (memory == NULL) in agp_allocate_memory_wrap()
285 return memory; in agp_allocate_memory_wrap()
365 while (memory) { in agp_remove_all_memory()
366 temp = memory; in agp_remove_all_memory()
367 memory = memory->next; in agp_remove_all_memory()
888 if (memory == NULL) in agpioc_allocate_wrap()
891 alloc.key = memory->key; in agpioc_allocate_wrap()
908 if (memory == NULL) in agpioc_deallocate_wrap()
926 if (memory == NULL) in agpioc_bind_wrap()
[all …]
|
| /openbmc/linux/Documentation/mm/ |
| H A D | page_tables.rst | 7 Paged virtual memory was invented along with virtual memory as a concept in
9 virtual memory. The feature migrated to newer computers and became a de facto
14 as seen on the external memory bus.
22 is the physical address of the page (as seen on the external memory bus)
25 Physical memory address 0 will be *pfn 0* and the highest pfn will be
26 the last page of physical memory the external address bus of the CPU can
45 become hierarchical and that in turn is done to save page table memory and
50 would be very sparse, because large portions of the virtual memory usually
58 shortcuts in mapping virtual memory to physical memory: there is no need to
89 mapping a single page of virtual memory to a single page of physical memory.
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | Dimm.interface.yaml | 19 Type of memory.
47 the corresponding data is made available by the memory module.
55 The base module type of the memory.
63 Speeds supported by this memory in megatransfers.
68 Memory Technology of this memory.
100 The memory module is comprised of volatile memory.
103 The memory module is comprised of volatile memory backed by
104 non-volatile memory.
107 The memory module is comprised of non-volatile memory.
111 and volatile memory.
[all …]
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | r8a7795-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";
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | kasan.rst | 68 stack, and global memory.
73 memory.
249 memory state section of the report shows the state of one of the memory
287 Generic KASAN dedicates 1/8th of kernel memory to its shadow memory (16TB
305 memory accesses are valid or not by checking corresponding shadow memory.
323 to store memory tags associated with each 16-byte memory cell (therefore, it
324 dedicates 1/16th of the kernel memory for shadow memory).
331 before each memory access. These checks make sure that the tag of the memory
352 shadow memory.
378 Shadow memory
[all …]
|
| /openbmc/linux/arch/arm64/boot/dts/ti/ |
| H A D | k3-j784s4-evm.dts | 32 memory@80000000 {
33 device_type = "memory";
39 reserved_memory: reserved-memory {
151 c71_0_memory_region: c71-memory@a8100000 {
163 c71_1_memory_region: c71-memory@a9100000 {
175 c71_2_memory_region: c71-memory@aa100000 {
187 c71_3_memory_region: c71-memory@ab100000 {
821 memory-region = <&c71_0_dma_memory_region>,
828 memory-region = <&c71_1_dma_memory_region>,
835 memory-region = <&c71_2_dma_memory_region>,
[all …]
|
| /openbmc/linux/arch/arm/boot/dts/calxeda/ |
| H A D | ecx-2000.dts | 54 memory@0 {
55 name = "memory";
56 device_type = "memory";
60 memory@200000000 {
61 name = "memory";
62 device_type = "memory";
76 memory-controller@fff00000 {
|
| /openbmc/linux/arch/arm/boot/dts/ti/omap/ |
| H A D | am572x-idk-common.dtsi | 12 memory@0 {
13 device_type = "memory";
17 reserved-memory {
22 ipu2_memory_region: ipu2-memory@95800000 {
29 dsp1_memory_region: dsp1-memory@99000000 {
36 ipu1_memory_region: ipu1-memory@9d000000 {
43 dsp2_memory_region: dsp2-memory@9f000000 {
187 memory-region = <&ipu2_memory_region>;
192 memory-region = <&ipu1_memory_region>;
197 memory-region = <&dsp1_memory_region>;
[all …]
|
| /openbmc/u-boot/lib/ |
| H A D | lmb.c | 20 debug(" memory.cnt = 0x%lx\n", lmb->memory.cnt); in lmb_dump_all()
22 (unsigned long long)lmb->memory.size); in lmb_dump_all()
23 for (i = 0; i < lmb->memory.cnt; i++) { in lmb_dump_all()
25 (unsigned long long)lmb->memory.region[i].base); in lmb_dump_all()
95 lmb->memory.cnt = 0; in lmb_init()
96 lmb->memory.size = 0; in lmb_init()
214 struct lmb_region *_rgn = &(lmb->memory); in lmb_add()
319 for (i = lmb->memory.cnt - 1; i >= 0; i--) { in __lmb_alloc_base()
370 lmb->memory.region[rgn].size, in lmb_alloc_addr()
401 return lmb->memory.region[lmb->memory.cnt - 1].base + in lmb_get_free_size()
[all …]
|