/openbmc/linux/tools/testing/memblock/tests/ |
H A D | common.c | 41 memset(memblock.memory.regions, 0, in reset_memblock_regions() 42 memblock.memory.cnt * sizeof(struct memblock_region)); in reset_memblock_regions() 43 memblock.memory.cnt = 1; in reset_memblock_regions() 44 memblock.memory.max = INIT_MEMBLOCK_REGIONS; in reset_memblock_regions() 45 memblock.memory.total_size = 0; in reset_memblock_regions() 56 memblock.memory.name = "memory"; in reset_memblock_attributes()
|
/openbmc/linux/Documentation/admin-guide/mm/ |
H A D | transhuge.rst | 8 Performance critical computing applications dealing with large memory 41 memory in turn reducing the number of TLB misses. With 70 deals with large amounts of memory. 84 risk to lose memory by using hugepages, should use 224 memory. A lower value can prevent THPs from being 226 THPs, and lower memory access performance. 365 going to be split under memory pressure. 392 system uses memory compaction to copy data around memory to free a 398 memory compaction so that a huge page is free for use. 401 is incremented if the system compacted memory and [all …]
|
H A D | numa_memory_policy.rst | 40 allocations across all nodes with "sufficient" memory, so as 173 NUMA memory policy supports the following 4 behavioral modes: 177 MPOL_DEFAULT is converted to the NULL memory policy in all 194 This mode specifies that memory must come from the set of 196 the node in the set with sufficient free memory that is 226 For allocation of anonymous pages and shared memory pages, 258 nodes changes after the memory policy has been defined. 322 nodemasks to specify memory policies using this flag should 325 memory nodes 0 to N-1, where N is the number of memory nodes the 401 or by prefaulting the entire shared memory region into memory and locking [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/net/ |
H A D | qcom,ipa.yaml | 59 - description: IPA shared memory 95 - description: Path leading to system memory 105 - const: memory 108 - const: memory 148 memory-region: 182 # memory-region must be specified 190 - memory-region 194 # memory-region must be specified. 201 - memory-region 235 memory-region = <&ipa_fw_mem>; [all …]
|
/openbmc/linux/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/ |
H A D | vmmgf100.c | 70 nvkm_kmap(pt->memory); in gf100_vmm_pgt_dma() 76 nvkm_done(pt->memory); in gf100_vmm_pgt_dma() 114 switch (nvkm_memory_target(pt->memory)) { in gf100_vmm_pgd_pde() 128 switch (nvkm_memory_target(pt->memory)) { in gf100_vmm_pgd_pde() 141 nvkm_kmap(pd->memory); in gf100_vmm_pgd_pde() 143 nvkm_done(pd->memory); in gf100_vmm_pgd_pde() 204 switch (nvkm_memory_target(pd->memory)) { in gf100_vmm_invalidate() 248 struct nvkm_memory *memory = map->memory; in gf100_vmm_valid() local 284 u32 tags = ALIGN(nvkm_memory_size(memory), 1 << 17) >> comp; in gf100_vmm_valid() 291 ret = nvkm_memory_tags_get(memory, device, tags, in gf100_vmm_valid() [all …]
|
H A D | vmmnv44.c | 33 tmp[0] = nvkm_ro32(pt->memory, pteo + 0x0); in nv44_vmm_pgt_fill() 34 tmp[1] = nvkm_ro32(pt->memory, pteo + 0x4); in nv44_vmm_pgt_fill() 35 tmp[2] = nvkm_ro32(pt->memory, pteo + 0x8); in nv44_vmm_pgt_fill() 36 tmp[3] = nvkm_ro32(pt->memory, pteo + 0xc); in nv44_vmm_pgt_fill() 116 nvkm_kmap(pt->memory); in nv44_vmm_pgt_dma() 140 nvkm_done(pt->memory); in nv44_vmm_pgt_dma() 150 nvkm_kmap(pt->memory); in nv44_vmm_pgt_unmap() 168 nvkm_done(pt->memory); in nv44_vmm_pgt_unmap()
|
/openbmc/linux/Documentation/core-api/ |
H A D | refcount-vs-atomic.rst | 14 ``atomic_*()`` functions with regards to the memory ordering guarantees. 17 these memory ordering guarantees. 20 tools/memory-model/Documentation/explanation.txt. 22 memory-barriers.txt and atomic_t.txt provide more background to the 23 memory ordering in general and for atomic operations specifically. 25 Relevant types of memory ordering 28 .. note:: The following section only covers some of the memory 31 please consult memory-barriers.txt document. 41 A strong (full) memory ordering guarantees that all prior loads and 49 A RELEASE memory ordering guarantees that all prior loads and [all …]
|
H A D | packing.rst | 10 One can memory-map a pointer to a carefully crafted struct over the hardware 11 device's memory region, and access its fields as struct members (potentially 22 still not protect from endianness mismatches, except if all memory accesses 34 - Packing a CPU-usable number into a memory buffer (with hardware 36 - Unpacking a memory buffer (which has hardware constraints/quirks) 45 logically. The question is: where do we lay this bit out in memory? 47 The following examples cover the memory layout of a packed u64 field. 61 LSByte (0) of the u64 sits at memory offset 7. 89 Therefore, QUIRK_LITTLE_ENDIAN means that inside the memory region, every 113 In this case the 8 byte memory region is interpreted as follows: first [all …]
|
/openbmc/linux/drivers/base/ |
H A D | memory.c | 662 memory->dev.bus = &memory_subsys; in __add_memory_block() 663 memory->dev.id = memory->start_section_nr / sections_per_block; in __add_memory_block() 666 memory->dev.offline = memory->state == MEM_OFFLINE; in __add_memory_block() 670 put_device(&memory->dev); in __add_memory_block() 673 ret = xa_err(xa_store(&memory_blocks, memory->dev.id, memory, in __add_memory_block() 676 device_unregister(&memory->dev); in __add_memory_block() 832 if (memory->group) { in remove_memory_block() 833 list_del(&memory->group_next); in remove_memory_block() 834 memory->group = NULL; in remove_memory_block() 838 put_device(&memory->dev); in remove_memory_block() [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
H A D | st-rproc.txt | 14 - memory-region Reserved memory (See: ../reserved-memory/reserved-memory.txt) 35 memory-region = <&audio_reserved>;
|
H A D | ti,omap-remoteproc.yaml | 95 memory-region: 102 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt 117 internal RAM memory region. 229 reserved-memory { 233 dsp_memory_region: dsp-memory@98000000 { 247 memory-region = <&dsp_memory_region>; 262 reserved-memory { 266 ipu_memory_region: ipu-memory@95800000 { 284 memory-region = <&ipu_memory_region>; 299 reserved-memory { [all …]
|
/openbmc/linux/arch/arm/boot/dts/synaptics/ |
H A D | berlin2cd-google-chromecast.dts | 22 memory@0 { 23 device_type = "memory"; 26 * We're using "linux,usable-memory" instead of "reg" here 28 * with this device provides an incorrect memory range in 34 linux,usable-memory = <0x00000000 0x20000000>; /* 512 MB */
|
/openbmc/linux/lib/ |
H A D | Kconfig.kmsan | 6 # Clang versions <14.0.0 also support -fsanitize=kernel-memory, but not 9 def_bool $(cc-option,-fsanitize=kernel-memory -mllvm -msan-disable-checks=1) 24 because it drastically increases kernel memory footprint and slows 32 # -fsanitize-memory-param-retval is supported only by Clang >= 14. 34 def_bool $(cc-option,-fsanitize=kernel-memory -fsanitize-memory-param-retval) 41 If the compiler supports -fsanitize-memory-param-retval, KMSAN will
|
/openbmc/u-boot/test/lib/ |
H A D | lmb.c | 19 ut_asserteq(lmb->memory.cnt, 1); in check_lmb() 20 ut_asserteq(lmb->memory.region[0].base, ram_base); in check_lmb() 80 ut_asserteq(lmb.memory.cnt, 2); in test_multi_alloc() 81 ut_asserteq(lmb.memory.region[0].base, ram0); in test_multi_alloc() 83 ut_asserteq(lmb.memory.region[1].base, ram); in test_multi_alloc() 86 ut_asserteq(lmb.memory.cnt, 1); in test_multi_alloc() 87 ut_asserteq(lmb.memory.region[0].base, ram); in test_multi_alloc() 158 ut_asserteq(lmb.memory.cnt, 2); in test_multi_alloc() 161 ut_asserteq(lmb.memory.region[1].base, ram); in test_multi_alloc() 164 ut_asserteq(lmb.memory.cnt, 1); in test_multi_alloc() [all …]
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | ppc-memtrace | 13 Description: Write an integer containing the size in bytes of the memory 17 debugfs files will be created. Once memory is successfully 19 re-add memory to the kernel, echo 0 into this file (it will be 26 Description: This directory contains information about the removed memory 33 Description: This contains the size of the memory removed from the node. 39 Description: This contains the start address of the removed memory.
|
/openbmc/linux/Documentation/devicetree/bindings/firmware/ |
H A D | intel,stratix10-svc.txt | 30 - memory-region: 31 phandle to the reserved memory node. See 32 Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt 38 reserved-memory { 55 memory-region = <&service_reserved>;
|
/openbmc/linux/arch/arm64/boot/dts/qcom/ |
H A D | sdm845-lg-common.dtsi | 36 reserved-memory { 46 gpu_mem: memory@8c415000 { 51 ipa_fw_mem: memory@8c400000 { 56 adsp_mem: memory@8c500000 { 71 venus_mem: memory@96d00000 { 76 cdsp_mem: memory@97200000 { 86 slpi_mem: memory@97c00000 { 91 spss_mem: memory@99000000 { 97 memory@9d400000 { 103 memory@f0800000 { [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/edac/ |
H A D | aspeed-sdram-edac.txt | 3 The Aspeed BMC SoC supports DDR3 and DDR4 memory with and without ECC (error 6 The memory controller supports SECDED (single bit error correction, double bit 8 every 64 bit word (effectively reducing available memory to 8/9). 10 Note, the bootloader must configure ECC mode in the memory controller.
|
/openbmc/linux/Documentation/devicetree/bindings/memory-controllers/ |
H A D | calxeda-ddr-ctrlr.yaml | 4 $id: http://devicetree.org/schemas/memory-controllers/calxeda-ddr-ctrlr.yaml# 7 title: Calxeda DDR memory controller 10 The Calxeda DDR memory controller is initialised and programmed by the 38 memory-controller@fff00000 {
|
/openbmc/u-boot/arch/x86/dts/ |
H A D | skeleton.dtsi | 3 * add a compatible value. The bootloader will typically populate the memory 12 memory { device_type = "memory"; reg = <0 0>; };
|
/openbmc/u-boot/arch/arm/dts/ |
H A D | skeleton.dtsi | 3 * add a compatible value. The bootloader will typically populate the memory 12 memory { device_type = "memory"; reg = <0 0>; };
|
/openbmc/openbmc/meta-quanta/meta-s6q/recipes-phosphor/configuration/s6q-yaml-config/ |
H A D | ipmi-sensors.yaml | 107 path: /xyz/openbmc_project/metric/bmc/memory/available 527 path: /xyz/openbmc_project/metrics/memory/Memory Error 575 path: /xyz/openbmc_project/metrics/memory/MCERR 623 path: /xyz/openbmc_project/metrics/memory/Memory PPR 671 path: /xyz/openbmc_project/metrics/memory/XGMI Error 695 path: /xyz/openbmc_project/metrics/memory/POST Error 719 path: /xyz/openbmc_project/metrics/memory/PCI Error 743 path: /xyz/openbmc_project/metrics/memory/PCIe Error 767 path: /xyz/openbmc_project/metrics/memory/Critical INT 791 path: /xyz/openbmc_project/metrics/memory/SOC MISC [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/misc/ |
H A D | aspeed-p2a-ctrl.txt | 7 memory. The BMC can disable this bridge. If the bridge is enabled, the host 8 has read access to all the regions of memory, however the host only has read 21 - reg: A hint for the memory regions associated with the P2A controller 22 - memory-region: A phandle to a reserved_memory region to be used for the PCI 44 memory-region = <&reserved_memory>;
|
/openbmc/linux/Documentation/devicetree/bindings/crypto/ |
H A D | fsl,sec-v4.0.yaml | 127 addresses are checked by HW to monitor any change. If any memory is 162 that contains the memory address & length (combined) and a second 169 - const: fsl,sec-v5.4-rtic-memory 170 - const: fsl,sec-v5.0-rtic-memory 171 - const: fsl,sec-v4.0-rtic-memory 172 - const: fsl,sec-v4.0-rtic-memory 176 - description: RTIC memory address 246 compatible = "fsl,sec-v4.0-rtic-memory"; 251 compatible = "fsl,sec-v4.0-rtic-memory"; 256 compatible = "fsl,sec-v4.0-rtic-memory"; [all …]
|
/openbmc/qemu/docs/ |
H A D | nvdimm.txt | 7 The current QEMU only implements the persistent memory mode of vNVDIMM 13 The storage of a vNVDIMM device in QEMU is provided by the memory 14 backend (i.e. memory-backend-file and memory-backend-ram). A simple 34 - "object memory-backend-file,id=mem1,share=on,mem-path=$PATH, 68 1. Prior to QEMU v2.8.0, if memory-backend-file is used and the actual 82 change breaks the usage of memory-backend-file that only satisfies 86 architectures, so the broken memory-backend-file can work again. 102 If a memory backend file, which was previously used as the backend 125 1. Each hotplugged vNVDIMM device consumes one memory slot. Users 126 should always ensure the memory option "-m ...,slots=N" specifies [all …]
|