| /openbmc/linux/arch/microblaze/ |
| H A D | Kconfig | 132 aspects of kernel memory management.
140 bool "High memory support"
145 space as well as some memory mapped IO. That means that, if you
146 have a large amount of physical memory and/or IO, not all of the
147 memory can be "permanently mapped" by the kernel. The physical
148 memory that is not permanently mapped is called "high memory".
153 bool "Set maximum low memory"
157 will be used as "low memory", that is, memory which the kernel can
160 memory.
165 hex "Maximum low memory size (in bytes)" if LOWMEM_SIZE_BOOL
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | google,cros-ec-codec.yaml | 33 Physical base address and length of shared memory region from EC.
36 The last one integer is the length of the shared memory.
38 memory-region:
41 Shared memory region to EC. A "shared-dma-pool".
42 See ../reserved-memory/reserved-memory.txt for details.
73 memory-region = <&reserved_mem>;
|
| /openbmc/linux/arch/powerpc/boot/dts/fsl/ |
| H A D | qoriq-sec5.2-0.dtsi | 86 compatible = "fsl,sec-v5.2-rtic-memory",
87 "fsl,sec-v5.0-rtic-memory",
88 "fsl,sec-v4.0-rtic-memory";
93 compatible = "fsl,sec-v5.2-rtic-memory",
94 "fsl,sec-v5.0-rtic-memory",
95 "fsl,sec-v4.0-rtic-memory";
100 compatible = "fsl,sec-v5.2-rtic-memory",
101 "fsl,sec-v5.0-rtic-memory",
102 "fsl,sec-v4.0-rtic-memory";
108 "fsl,sec-v5.0-rtic-memory",
[all …]
|
| H A D | qoriq-sec5.3-0.dtsi | 86 compatible = "fsl,sec-v5.3-rtic-memory",
87 "fsl,sec-v5.0-rtic-memory",
88 "fsl,sec-v4.0-rtic-memory";
93 compatible = "fsl,sec-v5.3-rtic-memory",
94 "fsl,sec-v5.0-rtic-memory",
95 "fsl,sec-v4.0-rtic-memory";
100 compatible = "fsl,sec-v5.3-rtic-memory",
101 "fsl,sec-v5.0-rtic-memory",
102 "fsl,sec-v4.0-rtic-memory";
108 "fsl,sec-v5.0-rtic-memory",
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
| H A D | xlnx,zynqmp-r5fss.yaml | 45 tightly coupled memories (TCM). System memory is cacheable, but the TCM
46 memory space is non-cacheable.
48 Each RPU contains one 64KB memory and two 32KB memories that
51 TCM memory.
80 the RPU can execute instructions and access data from the OCM memory,
81 the main DDR memory, and other system memories.
87 memory-region:
89 List of phandles to the reserved memory regions associated with the
92 vrings, ...). This reserved memory region will be allocated in DDR memory.
122 … memory-region = <&rproc_0_fw_image>, <&rpu0vdev0buffer>, <&rpu0vdev0vring0>, <&rpu0vdev0vring1>;
[all …]
|
| H A D | ti,keystone-rproc.txt | 37 representing a specific internal memory region, and
90 - memory-region: phandle to the reserved memory node to be associated
94 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
113 /* 66AK2H/K DSP memory node */
114 reserved-memory {
119 dsp_common_memory: dsp-common-memory@81f800000 {
141 memory-region = <&dsp_common_memory>;
152 /* 66AK2G DSP memory node */
153 reserved-memory {
158 dsp_common_memory: dsp-common-memory@81f800000 {
[all …]
|
| H A D | ti,k3-dsp-rproc.yaml | 18 L1 and/or L2 caches/SRAMs, an Interrupt Controller, an external memory
62 memory-region:
67 device. There should be at least two reserved memory nodes defined. The
68 reserved memory nodes should be carveout nodes, and should be defined as
70 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt
101 - description: Address and Size of the L2 SRAM internal memory region
102 - description: Address and Size of the L1 PRAM internal memory region
103 - description: Address and Size of the L1 DRAM internal memory region
138 - memory-region
177 memory-region = <&c66_0_dma_memory_region>,
[all …]
|
| /openbmc/qemu/hw/xtensa/ |
| H A D | xtensa_memory.c | 34 void xtensa_create_memory_regions(const XtensaMemory *memory, in xtensa_create_memory_regions() argument
41 for (i = 0; i < memory->num; ++i) { in xtensa_create_memory_regions()
47 memory->location[i].size, &error_fatal); in xtensa_create_memory_regions()
48 memory_region_add_subregion(super, memory->location[i].addr, m); in xtensa_create_memory_regions()
|
| /openbmc/linux/drivers/media/platform/samsung/exynos4-is/ |
| H A D | fimc-is.c | 339 &is->memory.addr, GFP_KERNEL); in fimc_is_alloc_cpu_memory()
340 if (is->memory.vaddr == NULL) in fimc_is_alloc_cpu_memory()
343 is->memory.size = FIMC_IS_CPU_MEM_SIZE; in fimc_is_alloc_cpu_memory()
349 (u32)is->memory.addr); in fimc_is_alloc_cpu_memory()
350 dma_free_coherent(dev, is->memory.size, is->memory.vaddr, in fimc_is_alloc_cpu_memory()
351 is->memory.addr); in fimc_is_alloc_cpu_memory()
358 is->is_dma_p_region = is->memory.addr + in fimc_is_alloc_cpu_memory()
370 if (is->memory.vaddr == NULL) in fimc_is_free_cpu_memory()
373 dma_free_coherent(dev, is->memory.size, is->memory.vaddr, in fimc_is_free_cpu_memory()
374 is->memory.addr); in fimc_is_free_cpu_memory()
[all …]
|
| /openbmc/linux/drivers/cxl/ |
| H A D | Kconfig | 13 memory targets, the CXL.io protocol is equivalent to PCI Express.
23 The CXL specification defines a "CXL memory device" sub-class in the
26 memory to be mapped into the system address map (Host-managed Device
29 Say 'y/m' to enable a driver that will attach to CXL memory expander
50 potential impact to memory currently in use by the kernel.
60 Enable support for host managed device memory (HDM) resources
77 support for persistent memory attached via CXL. This support is
80 provisioning the persistent memory capacity of CXL memory expanders.
91 memory were attached to the typical CPU memory controller. This is
119 platform-firmware this option enables memory error handling to
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/reserved-memory/ |
| H A D | google,open-dice.yaml | 4 $id: http://devicetree.org/schemas/reserved-memory/google,open-dice.yaml#
10 This binding represents a reserved memory region containing data
19 - $ref: reserved-memory.yaml
26 description: page-aligned region of memory containing DICE data
37 reserved-memory {
|
| /openbmc/linux/Documentation/driver-api/pci/ |
| H A D | p2pdma.rst | 24 memory that is used for P2P transactions needs to be backed by struct
37 memory or doorbell registers to other drivers.
54 can DMA directly to the memory exposed by the NVMe device.
62 then the NVMe Target could use the RNIC's memory instead of the CMB
71 This will register struct pages for all the specified memory.
74 P2P memory using :c:func:`pci_p2pmem_publish()`. This will allow
75 any orchestrator drivers to find and use the memory. When marked in
76 this way, the resource must be regular memory with no side effects.
88 will do the right thing for the P2P capable memory.
112 allocating scatter-gather lists with P2P memory.
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | numastat.rst | 10 are able to allocate memory from nodes they prefer. If they succeed, numa_hit
25 numa_hit A process wanted to allocate memory from this node,
28 numa_miss A process wanted to allocate memory from another node,
29 but ended up with memory from this node.
32 but ended up with memory from another node.
35 and got memory from this node.
38 and got memory from this node.
49 memory) the numa_hit, numa_miss and numa_foreign statistics can be skewed
52 implementation actually treats one of the nearest nodes with memory as the
|
| /openbmc/linux/Documentation/fault-injection/ |
| H A D | notifier-error-inject.rst | 31 bash: echo: write error: Cannot allocate memory
37 /sys/kernel/debug/notifier-error-inject/memory/actions/<notifier event>/error
39 Possible memory notifier events to be failed are:
44 Example: Inject memory hotplug offline error (-12 == -ENOMEM)::
46 # cd /sys/kernel/debug/notifier-error-inject/memory
48 # echo offline > /sys/devices/system/memory/memoryXXX/state
49 bash: echo: write error: Cannot allocate memory
92 for CPU and memory notifiers.
95 * tools/testing/selftests/memory-hotplug/mem-on-off-test.sh
|
| /openbmc/u-boot/drivers/video/stm32/ |
| H A D | Kconfig | 17 int "Maximum horizontal resolution (for memory allocation purposes)"
22 This configuration is used for reserving/allocating memory for the
26 int "Maximum vertical resolution (for memory allocation purposes)"
31 This configuration is used for reserving/allocating memory for the
35 int "Maximum bits per pixel (for memory allocation purposes)"
40 This configuration is used for reserving/allocating memory for the
|
| /openbmc/linux/Documentation/security/ |
| H A D | self-protection.rst | 14 has arbitrary read and write access to the kernel's memory. In many
38 memory, etc.
40 Strict kernel memory permissions
91 access to the memory.)
93 Segregation of kernel memory from userspace memory
101 cannot be passed to trivially-controlled userspace memory, forcing
102 attacks to operate entirely in kernel memory.
172 Heap memory integrity
177 other memory areas.
227 discover desired memory locations.)
[all …]
|
| /openbmc/linux/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/ |
| H A D | uvmm.c | 160 struct nvkm_memory *memory; in nvkm_uvmm_mthd_map() local
166 handle = args->v0.memory; in nvkm_uvmm_mthd_map()
175 if (IS_ERR(memory)) { in nvkm_uvmm_mthd_map()
177 return PTR_ERR(memory); in nvkm_uvmm_mthd_map()
218 nvkm_memory_unref(&memory); in nvkm_uvmm_mthd_map()
227 nvkm_memory_unref(&memory); in nvkm_uvmm_mthd_map()
401 struct nvkm_memory *memory; in nvkm_uvmm_mthd_raw_map() local
404 u64 handle = args->memory; in nvkm_uvmm_mthd_raw_map()
417 memory = nvkm_umem_search(client, args->memory); in nvkm_uvmm_mthd_raw_map()
418 if (IS_ERR(memory)) { in nvkm_uvmm_mthd_raw_map()
[all …]
|
| /openbmc/linux/arch/powerpc/boot/ |
| H A D | treeboot-iss4xx.c | 37 void *memory; in iss_4xx_fixups() local
40 memory = finddevice("/memory"); in iss_4xx_fixups()
41 if (!memory) in iss_4xx_fixups()
44 getprop(memory, "reg", reg, sizeof(reg)); in iss_4xx_fixups()
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | kasan.txt | 8 The shadow area sits at the top of the kernel virtual memory space above the
9 fixmap area and occupies one eighth of the total kernel virtual memory space.
35 - Therefore any offset has to point to memory that is valid with
47 - We'd like to place it near the start of physical memory. In theory we can do
48 this at run-time based on how much physical memory we have, but this requires
53 - Alternatively, we can place the shadow at the _end_ of memory, but this
54 requires knowing how much contiguous physical memory a system has _at compile
56 to handle discontiguous physical memory, total failure to boot on machines
57 with less memory than specified, and that machines with more memory than
|
| /openbmc/linux/arch/arm/boot/dts/ti/keystone/ |
| H A D | keystone-k2hk-evm.dts | 16 reserved-memory {
21 dsp_common_memory: dsp-common-memory@81f800000 {
199 memory-region = <&dsp_common_memory>;
204 memory-region = <&dsp_common_memory>;
209 memory-region = <&dsp_common_memory>;
214 memory-region = <&dsp_common_memory>;
219 memory-region = <&dsp_common_memory>;
224 memory-region = <&dsp_common_memory>;
229 memory-region = <&dsp_common_memory>;
234 memory-region = <&dsp_common_memory>;
|
| /openbmc/linux/tools/testing/memblock/tests/ |
| H A D | alloc_exact_nid_api.c | 31 struct memblock_region *req_node = &memblock.memory.regions[nid_req]; in alloc_exact_nid_top_down_numa_simple_check()
83 struct memblock_region *req_node = &memblock.memory.regions[nid_req]; in alloc_exact_nid_top_down_numa_part_reserved_check()
202 struct memblock_region *node2 = &memblock.memory.regions[6]; in alloc_exact_nid_top_down_numa_no_overlap_split_check()
260 struct memblock_region *min_node = &memblock.memory.regions[2]; in alloc_exact_nid_top_down_numa_no_overlap_low_check()
261 struct memblock_region *max_node = &memblock.memory.regions[5]; in alloc_exact_nid_top_down_numa_no_overlap_low_check()
473 struct memblock_region *node2 = &memblock.memory.regions[6]; in alloc_exact_nid_bottom_up_numa_no_overlap_split_check()
531 struct memblock_region *min_node = &memblock.memory.regions[2]; in alloc_exact_nid_bottom_up_numa_no_overlap_low_check()
532 struct memblock_region *max_node = &memblock.memory.regions[5]; in alloc_exact_nid_bottom_up_numa_no_overlap_low_check()
754 struct memblock_region *min_node = &memblock.memory.regions[2]; in alloc_exact_nid_numa_no_overlap_high_generic_check()
755 struct memblock_region *max_node = &memblock.memory.regions[5]; in alloc_exact_nid_numa_no_overlap_high_generic_check()
[all …]
|
| /openbmc/linux/Documentation/translations/zh_CN/accounting/ |
| H A D | psi.rst | 16 当CPU、memory或IO设备处于竞争状态，业务负载会遭受时延毛刺、吞吐量降低，
37 压力信息可通过/proc/pressure/ --cpu、memory、io文件分别获取。
74 示例：向/proc/pressure/memory写入"some 150000 1000000"将新增触发器，将在
112 fds.fd = open("/proc/pressure/memory", O_RDWR | O_NONBLOCK);
114 printf("/proc/pressure/memory open error: %s\n",
121 printf("/proc/pressure/memory write error: %s\n",
152 此场景下cgroupfs挂载点的子目录包含cpu.pressure、memory.pressure、io.pressure文件，
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/fsl/ |
| H A D | bman.txt | 67 BMan requires a contiguous range of physical memory used for the backing store
68 for BMan Free Buffer Proxy Records (FBPR). This memory is reserved/allocated as
69 a node under the /reserved-memory node.
71 The BMan FBPR memory node must be named "bman-fbpr"
82 The following constraints are relevant to the FBPR private memory:
85 - The alignment must be a muliptle of the memory size
93 For additional details about reserved memory regions see reserved-memory.txt
97 The example below shows a BMan FBPR dynamic allocation memory node
99 reserved-memory {
130 memory-region = <&bman_fbpr>;
|
| /openbmc/u-boot/doc/ |
| H A D | README.unaligned-memory-access.txt | 8 when it comes to memory access. This document presents some details about
19 reading 4 bytes of data from address 0x10005 would be an unaligned memory
22 The above may seem a little vague, as memory access can happen in different
24 or write a number of bytes to or from memory (e.g. movb, movw, movl in x86
34 When accessing N bytes of memory, the base memory address must be evenly
41 of memory access. However, we must consider ALL supported architectures;
53 - Some architectures are able to perform unaligned memory accesses
66 memory accesses to happen, your code will not work correctly on certain
75 memory addresses of certain variables, etc.
164 2 bytes (16 bits) to be read from memory starting at address addr1.
[all …]
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | kmsan.rst | 40 Uninit was stored to memory at:
125 KMSAN shadow memory
130 kernel memory byte is uninitialized. Marking the memory uninitialized (i.e.
144 length. When a constant value is written into memory, that memory is unpoisoned.
145 When a value is read from memory, its shadow memory is also obtained and
185 memory.
244 values are read from memory. When a value is stored to memory, its shadow and
323 , which unpoisons the memory region.
388 boundary of a memory block, accesses to shadow/origin memory may potentially
407 2. For vmalloc memory and modules, there is a direct mapping between the memory
[all …]
|