Home
last modified time | relevance | path

Searched refs:memory (Results 1 – 25 of 1444) sorted by relevance

12345678910>>...58

/openbmc/qemu/docs/
H A Dmemory-hotplug.txt1 QEMU memory hotplug
4 This document explains how to use the memory hotplug feature in QEMU,
7 Guest support is required for memory hotplug to work.
12 In order to be able to hotplug memory, QEMU has to be told how many
13 hotpluggable memory slots to create and what is the maximum amount of
14 memory the guest can grow. This is done at startup time by means of
22 - "slots" is the number of hotpluggable memory slots
29 Creates a guest with 1GB of memory and three hotpluggable memory slots.
30 The hotpluggable memory slots are empty when the guest is booted, so all
31 memory the guest will see after boot is 1GB. The maximum memory the
[all …]
/openbmc/qemu/tests/multiboot/
H A Dmmap.out6 Lower memory: 639k
7 Upper memory: 129920k
9 e820 memory map:
24 Lower memory: 639k
25 Upper memory: 104k
27 e820 memory map:
41 Lower memory: 639k
42 Upper memory: 2096000k
44 e820 memory map:
59 Lower memory: 639k
[all …]
/openbmc/qemu/tests/tcg/multiarch/system/
H A DMakefile.softmmu-target25 run-gdbstub-memory: memory
32 --bin $< --test $(MULTIARCH_SRC)/gdbstub/memory.py, \
57 run-gdbstub-registers: memory
71 MULTIARCH_RUNS += run-gdbstub-memory run-gdbstub-interrupt \
76 run-plugin-memory-with-libmem.so: memory libmem.so
77 run-plugin-memory-with-libmem.so: PLUGIN_ARGS=$(COMMA)region-summary=true
78 run-plugin-memory-with-libmem.so: CHECK_PLUGIN_OUTPUT_COMMAND=$(MULTIARCH_SYSTEM_SRC)/validate-memo…
80 EXTRA_RUNS_WITH_PLUGIN += run-plugin-memory-with-libmem.so
/openbmc/qemu/tests/tcg/arm/
H A DMakefile.softmmu-target45 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/u-boot/arch/arm/dts/
H A Dr8a7795-h3ulcb.dts17 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 Dr8a7795-salvator-x.dts16 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 Dr8a7796-m3ulcb.dts17 memory@48000000 {
18 device_type = "memory";
23 memory@600000000 {
24 device_type = "memory";
/openbmc/qemu/tests/tcg/aarch64/
H A DMakefile.softmmu-target46 memory: CFLAGS+=-DCHECK_UNALIGNED=1
48 memory-sve: memory.c $(LINK_SCRIPT) $(CRT_OBJS) $(MINILIB_OBJS)
51 memory-sve: CFLAGS+=-DCHECK_UNALIGNED=1 -march=armv8.1-a+sve -O3
53 TESTS+=memory-sve
75 .PHONY: memory-record
76 run-memory-record: memory-record memory
81 $(QEMU_OPTS) memory)
83 .PHONY: memory-replay
84 run-memory-replay: memory-replay run-memory-record
89 $(QEMU_OPTS) memory)
[all …]
/openbmc/qemu/docs/system/devices/
H A Divshmem.rst4 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 …]
H A Dvirtio-pmem.rst7 The virtio pmem device is a paravirtualized persistent memory device
14 host page cache. This reduces guest memory footprint as the host can
15 make efficient memory reclaim decisions under memory pressure.
28 A virtio pmem device backed by a memory-backend-file can be created on
31 -object memory-backend-file,id=mem1,share,mem-path=./virtio_pmem.img,size=4G
36 - "object memory-backend-file,id=mem1,share,mem-path=<image>, size=<image size>"
40 pci device whose storage is provided by above memory backend device.
49 memory backing has to be added via 'object_add'; afterwards, the virtio
55 (qemu) object_add memory-backend-file,id=mem2,share=on,mem-path=virtio_pmem2.img,size=4G
H A Dcxl.rst4 targets accelerators and memory devices attached to a CXL host.
27 - BAR mapped memory accesses used for registers and mailboxes.
37 supported by the host for normal memory should also work for
38 CXL attached memory devices.
49 **Type 1:** These support coherent caching of host memory. Example might
50 be a crypto accelerators. May also have device private memory accessible
51 via means such as PCI memory reads and writes to BARs.
53 **Type 2:** These support coherent caching of host memory and host
54 managed device memory (HDM) for which the coherency protocol is managed
59 additional memory (HDM) to a CXL host including both volatile and
[all …]
/openbmc/qemu/docs/specs/
H A Dacpi_mem_hotplug.rst1 QEMU<->ACPI BIOS memory hotplug interface
4 ACPI BIOS GPE.3 handler is dedicated for notifying OS about memory hot-add
14 Lo part of memory device phys address
16 Hi part of memory device phys address
18 Lo part of memory device size in bytes
20 Hi part of memory device size in bytes
48 Memory device slot selector, selects active memory device.
50 region will read/store data from/to selected memory device.
70 selected memory device
74 selected memory device
[all …]
/openbmc/u-boot/doc/device-tree-bindings/memory-controllers/
H A Dst,stm32-fmc.txt1 ST, stm32 flexible memory controller Drive
6 u-boot,dm-pre-reloc: flag to initialize memory before relocation.
8 on-board sdram memory attributes:
12 memory width
13 number of intenal banks in memory
27 include/dt-bindings/memory/stm32-sdram.h to define sdram control and timing
43 /* sdram memory configuration from sdram datasheet */
51 /* sdram memory configuration from sdram datasheet */
/openbmc/qemu/qapi/
H A Ddump.json9 # Dump guest memory
16 # An enumeration of guest-memory-dump's format.
51 # @dump-guest-memory:
53 # Dump guest's memory to vmcore. It is a synchronous operation that
54 # can take very long depending on the amount of guest memory.
56 # @paging: if true, do paging to get guest's memory mapping. This
66 # corrupted memory, which cannot be trusted
86 # @length: if specified, the memory size, in bytes. If you don't want
87 # to dump all guest's memory, please specify the start @begin and
90 # @format: if specified, the format of guest memory dump. But non-elf
[all …]
/openbmc/qemu/docs/system/
H A Dvm-templating.rst6 For now, the focus is on VM memory aspects, and not about how to save and
14 in fast startup times and reduced memory consumption.
18 new VMs are able to read template VM memory; however, any modifications
36 In order to create the template VM, we have to make sure that VM memory
39 Supply VM RAM via memory-backend-file, with ``share=on`` (modifications go
49 -object memory-backend-file,id=pc.ram,mem-path=template,size=2g,share=on,... \\
50 -machine q35,memory-backend=pc.ram
52 If multiple memory backends are used (vNUMA, DIMMs), configure all
53 memory backends accordingly.
62 Supply VM RAM via memory-backend-file, with ``share=off`` (modifications
[all …]
/openbmc/qemu/docs/devel/
H A Dmemory.rst2 The memory API
5 The memory API models the memory and I/O buses and controllers of a QEMU
9 - memory-mapped I/O (MMIO)
10 - memory controllers that can dynamically reroute physical memory regions
13 The memory model provides support for
16 - setting up coalesced memory for kvm
21 buses, memory controllers, and memory regions that have been rerouted.
23 In addition to MemoryRegion objects, the memory API provides AddressSpace
25 These represent memory as seen from the CPU or a device's viewpoint.
30 There are multiple types of memory regions (all represented by a single C type
[all …]
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/
H A D0052-reserve-memory-for-se-comm.patch4 Subject: [PATCH] arm-bsp/u-boot: Reserve memory for RSS comm pointer access protocol
6 This memory was used by OpenAMP to establish communication between
8 OpenAMP to RSE_COMMS, this shared memory is now configured for the
11 Since this memory may be still used by a user-space application
12 in linux as U-Boot is passing an EFI memory map starting from
13 0x80000000, this memory range should be reserved as the
31 + reserved-memory {
/openbmc/u-boot/doc/device-tree-bindings/clock/
H A Drockchip,rk3368-dmc.txt1 RK3368 dynamic memory controller driver
4 The RK3368 DMC (dynamic memory controller) driver supports setup/initialisation
7 (a) a target-frequency (i.e. operating point) for the memory operation
9 (c) a memory-schedule (i.e. mapping from physical addresses to the address
10 pins of the memory bus)
44 - rockchip,memory-schedule:
54 #include <dt-bindings/memory/rk3368-dmc.h>
66 rockchip,memory-schedule = <DMC_MSCH_CBRD>;
/openbmc/u-boot/doc/device-tree-bindings/memory/
H A Dmemory.txt3 The memory binding for U-Boot is as in the ePAPR with the following additions:
5 Optional subnodes can be used defining the memory layout for different board
11 If subnodes are present, then the /memory node must define these properties:
19 memory-banks - list of memory banks in the same format as normal
37 memory {
65 * Default of 2GB of memory, auto-sized, so could be smaller
66 * 3.5GB of memory (with no auto-size) if (board id & 2) is 2
67 * 1GB of memory (with no auto-size) if board id is 17.
/openbmc/qemu/hw/xtensa/
H A Dxtensa_memory.c34 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/u-boot/lib/
H A Dlmb.c20 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()
27 (unsigned long long)lmb->memory.region[i].size); 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()
320 phys_addr_t lmbbase = lmb->memory.region[i].base; in __lmb_alloc_base()
[all …]
/openbmc/u-boot/doc/
H A DREADME.memory-test2 hardware, or when using a sloppy port on some board, is memory errors.
4 incorrect initialization of the memory controller. So it appears to
5 be a good idea to always test if the memory is working correctly,
8 U-Boot implements 3 different approaches to perform memory tests:
14 memory banks on this piece of hardware. The code is supposed to be
17 catch 99% of hardware related (i. e. reliably reproducible) memory
23 This is probably the best known memory test utility in U-Boot.
35 no knowledge about memory ranges that may be in use for other
46 system memory) and for U-Boot (code, data, etc. - see above;
47 these are usually at the very upper end of system memory). But
[all …]
/openbmc/u-boot/drivers/video/stm32/
H A DKconfig17 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/openbmc/meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools/core/
H A D0001-memory.h-Always-define-strlcpy-for-glibc-based-syste.patch4 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/u-boot/doc/usage/
H A Dmeasured_boot.rst8 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

12345678910>>...58