Home
last modified time | relevance | path

Searched full:memory (Results 1 – 25 of 4181) sorted by relevance

12345678910>>...168

/openbmc/qemu/include/hw/mem/
H A Dmemory-device.h2 * Memory Device Interface
20 #define TYPE_MEMORY_DEVICE "memory-device"
33 * All memory devices need to implement TYPE_MEMORY_DEVICE as an interface.
35 * A memory device is a device that owns a memory region which is
37 * address in guest physical memory can either be specified explicitly
40 * Some memory device might not own a memory region in certain device
42 * empty memory devices are mostly ignored by the memory device code.
44 * Conceptually, memory devices only span one memory region. If multiple
45 * successive memory regions are used, a covering memory region has to
46 * be provided. Scattered memory regions are not supported for single
[all …]
/openbmc/openbmc/meta-quanta/meta-s6q/recipes-phosphor/configuration/s6q-yaml-config/
H A Dipmi-sensors.yaml107 path: /xyz/openbmc_project/metric/bmc/memory/available
527 path: /xyz/openbmc_project/metrics/memory/Memory Error
534 xyz.openbmc_project.Memory.MemoryECC:
539 assert: xyz.openbmc_project.Memory.MemoryECC.ECCStatus.CE
542 assert: xyz.openbmc_project.Memory.MemoryECC.ECCStatus.UE
545 assert: xyz.openbmc_project.Memory.MemoryECC.ECCStatus.LogFull
551 path: /xyz/openbmc_project/metrics/memory/Other IIO Error
558 xyz.openbmc_project.Memory.MemoryECC:
563 assert: xyz.openbmc_project.Memory.MemoryECC.ECCStatus.CE
566 assert: xyz.openbmc_project.Memory.MemoryECC.ECCStatus.UE
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/
H A DMemory_v1.xml4 <!--# Redfish Schema: Memory v1.21.0 -->
73 <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="Memory">
77 <EntityType Name="Memory" BaseType="Resource.v1_0_0.Resource" Abstract="true">
78 …<Annotation Term="OData.Description" String="The `Memory` schema represents a memory device, such …
79 …<Annotation Term="OData.LongDescription" String="This resource shall represent a memory device in …
98 <String>/redfish/v1/Systems/{ComputerSystemId}/Memory/{MemoryId}</String>
100 <String>/redfish/v1/Chassis/{ChassisId}/Memory/{MemoryId}</String>
101 … <String>/redfish/v1/CompositionService/ResourceBlocks/{ResourceBlockId}/Memory/{MemoryId}</String>
102 …itionService/ResourceBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Memory/{MemoryId}</String>
103 <String>/redfish/v1/ResourceBlocks/{ResourceBlockId}/Memory/{MemoryId}</String>
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DMemory_v1.xml4 <!--# Redfish Schema: Memory v1.21.0 -->
73 <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="Memory">
77 <EntityType Name="Memory" BaseType="Resource.v1_0_0.Resource" Abstract="true">
78 …<Annotation Term="OData.Description" String="The `Memory` schema represents a memory device, such …
79 …<Annotation Term="OData.LongDescription" String="This resource shall represent a memory device in …
98 <String>/redfish/v1/Systems/{ComputerSystemId}/Memory/{MemoryId}</String>
100 <String>/redfish/v1/Chassis/{ChassisId}/Memory/{MemoryId}</String>
101 … <String>/redfish/v1/CompositionService/ResourceBlocks/{ResourceBlockId}/Memory/{MemoryId}</String>
102 …itionService/ResourceBlocks/{ResourceBlockId}/Systems/{ComputerSystemId}/Memory/{MemoryId}</String>
103 <String>/redfish/v1/ResourceBlocks/{ResourceBlockId}/Memory/{MemoryId}</String>
[all …]
H A DMemoryRegion_v1.xml41 …cription" String="The `MemoryRegion` schema contains the definition of a memory region and its con…
42 …<Annotation Term="OData.LongDescription" String="This resource shall represent a memory region in …
74 <Annotation Term="OData.Description" String="The type of memory region."/>
75 …tion Term="OData.LongDescription" String="This property shall contain the type of memory region."/>
80 <Annotation Term="OData.Description" String="The memory region number."/>
81 …<Annotation Term="OData.LongDescription" String="This property shall contain the memory region num…
85 … <Annotation Term="OData.Description" String="The memory region block size in mebibytes (MiB)."/>
86 …<Annotation Term="OData.LongDescription" String="This property shall contain the memory region blo…
91 … <Annotation Term="OData.Description" String="The size of the memory region in mebibytes (MiB)."/>
92 …ata.LongDescription" String="This property shall contain the size of the memory region in mebibyte…
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/
H A DDimm.interface.yaml7 Data width of Memory.
11 Memory size of DIMM in Kilobyte.
15 Socket on base board where Memory located, for example CPU1_DIMM_B1.
19 Type of memory.
23 Additional detail on Memory, such as Synchronous, Static column, etc.
27 The maximum capable clock speed of Memory, in megahertz.
31 Rank attributes of Memory. Means how many groups of memory chips on
36 Configured clock speed to Memory, in megahertz.
46 strobe signal are presented to the memory module and the time at which
47 the corresponding data is made available by the memory module.
[all …]
H A DPersistentMemory.interface.yaml2 Implement to provide Persistent memory attributes.
7 The manufacturer ID of this memory module as defined by JEDEC in
12 The product ID of this memory module as defined by JEDEC in JEP-106.
16 The manufacturer ID of the memory subsystem controller of this memory
21 The product ID of the memory subsystem controller of this memory
34 Total size of the volatile portion memory in kibibytes (KiB).
38 Total size of the non-volatile portion memory in kibibytes (KiB).
42 Total size of the cache portion memory in kibibytes (KiB).
54 The size of the smallest unit of allocation for a memory region in
59 The boundary that memory regions are allocated on, measured in
[all …]
/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/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DMemoryRegion.v1_0_3.json36 "description": "Definition of memory chunk providing capacity for memory region.",
37 …ription": "This type shall contain the definition of a memory chunk providing capacity for memory …
55 … "description": "The link to the memory chunk providing capacity to the memory region.",
56 … contain a link to a resource of type `MemoryChunks` that provides capacity to the memory region.",
60 … "description": "Offset of the memory chunk within the memory region in mebibytes (MiB).",
61 …ion": "The value of this property shall be the offset of the memory chunk within the memory region…
71 …"description": "Definition of memory extent identifying an available address range in the memory r…
72 … shall contain the definition of a memory extent identifying an available address range in the dyn…
89 … "description": "Offset of the memory extent within the memory region in mebibytes (MiB).",
90 …ion": "The value of this property shall be the offset of the memory extent within the memory regio…
[all …]
H A DMemory.v1_21_0.json2 "$id": "http://redfish.dmtf.org/schemas/v1/Memory.v1_21_0.json",
3 "$ref": "#/definitions/Memory",
26 "#Memory.DisableMasterPassphrase": {
29 "#Memory.DisablePassphrase": {
32 "#Memory.FreezeSecurityState": {
35 "#Memory.InjectPersistentPoison": {
38 "#Memory.OverwriteUnit": {
41 "#Memory.Reset": {
44 "#Memory.ResetToDefaults": {
47 "#Memory.ScanMedia": {
[all …]
H A DMemoryChunks.v1_6_2.json42 "Block": "Block accessible memory.",
43 "PMEM": "Byte accessible persistent memory.",
44 "Volatile": "Volatile memory."
50 "description": "This an interleave set for a memory chunk.",
51 …"longDescription": "This type shall describe an interleave set of which the memory chunk is a part…
67 "Memory": { object
69 "description": "Describes a memory device of the interleave set.",
70 … "longDescription": "This property shall contain the memory device to which these settings apply.",
74 "description": "Level of the interleave set for multi-level tiered memory.",
75 …on": "This property shall contain the level of this interleave set for multi-level tiered memory.",
[all …]
H A DMemoryMetrics.v1_7_3.json39 …"description": "The alarm trip information about the memory. These alarms are reset when the syst…
40 …roperties that describe the types of alarms that have been raised by the memory. These alarms sha…
168 "description": "The memory metrics specific to CXL devices.",
169 … "longDescription": "This type shall contain the memory metrics specific to CXL devices.",
235 … "description": "The memory metrics since the last system reset or `ClearCurrentPeriod` action.",
236 …"longDescription": "This type shall describe the memory metrics since last system reset or `ClearC…
254 …nate to the `MemorySummary` object, this property shall be the sum of BlocksRead over all memory.",
263 …e to the `MemorySummary` object, this property shall be the sum of BlocksWritten over all memory.",
272 …emorySummary` object, this property shall be the sum of CorrectableECCErrorCount over all memory.",
282 …ors across all memory without duplication, which may not be the sum of all `IndeterminateCorrectab…
[all …]
H A DMemoryDomain.v1_5_1.json55 … "description": "An array of links to the CXL logical devices associated with this memory domain.",
59 …ogicalDevice` that represent the CXL logical devices that are associated with this memory domain.",
68 …escription": "An array of links to the fabric adapters that present this memory domain to a fabric…
72 …ype `FabricAdapter` that represent the fabric adapters that present this memory domain to a fabric…
82 … "description": "An array of links to the media controllers for this memory domain.",
86 …rray of links to resources of type `MediaController` that are associated with this memory domain.",
101 … "description": "An array of links to the PCIe functions representing this memory domain.",
105 …sources of type `PCIeFunction` that represent the PCIe functions representing this memory domain.",
118 …memory domain and its configuration. Memory domains indicate to the client which memory, or DIMMs…
119 … "longDescription": "This resource shall represent memory domains in a Redfish implementation.",
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DMemory.v1_21_0.json2 "$id": "http://redfish.dmtf.org/schemas/v1/Memory.v1_21_0.json",
3 "$ref": "#/definitions/Memory",
26 "#Memory.DisableMasterPassphrase": {
29 "#Memory.DisablePassphrase": {
32 "#Memory.FreezeSecurityState": {
35 "#Memory.InjectPersistentPoison": {
38 "#Memory.OverwriteUnit": {
41 "#Memory.Reset": {
44 "#Memory.ResetToDefaults": {
47 "#Memory.ScanMedia": {
[all …]
/openbmc/libcper/specification/json/sections/
H A Dcper-memory.json4 "description": "Memory Error Section",
10 "description": "Memory error status information.",
15 "description": "The bank number of the memory associated with the error.",
67 "description": "The physical address at which the memory error occurred."
78 …cription": "In a multi-node system, this value identifies the node containing the memory in error."
82 "description": "The card number of the memory error location."
86 "description": "The module or rank number of the memory error location."
90 "description": "The device number of the memory associated with the error."
94 "description": "The row number of the memory error location."
98 "description": "The column number of the memory error location."
[all …]
H A Dcper-memory2.json10 "description": "Memory error status information.",
15 "description": "The bank number of the memory associated with the error.",
51 "description": "Memory error status information.",
65 "description": "The physical address at which the memory error occurred."
76 …cription": "In a multi-node system, this value identifies the node containing the memory in error."
80 "description": "The card number of the memory error location."
84 "description": "The module number of the memory error location."
88 "description": "The device number of the memory associated with the error."
92 "description": "The row number of the memory error location."
96 "description": "The column number of the memory error location."
[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
19 Memory is modelled as an acyclic graph of MemoryRegion objects. Sinks
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.
[all …]
/openbmc/qemu/include/standard-headers/linux/
H A Dvirtio_mem.h50 * "resizable DIMM" consisting of small memory blocks that can be plugged
51 * or unplugged. The device driver is responsible for (un)plugging memory
54 * Virtio-mem devices can only operate on their assigned memory region in
55 * order to (un)plug memory. A device cannot (un)plug memory belonging to
58 * The "region_size" corresponds to the maximum amount of memory that can
59 * be provided by a device. The "size" corresponds to the amount of memory
63 * "requested_size". It is impossible to plug more memory than requested.
65 * The "usable_region_size" represents the memory region that can actually
66 * be used to (un)plug memory. It is always at least as big as the
70 * There are no guarantees what will happen if unplugged memory is
[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
33 Memory configuration
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.
[all …]
/openbmc/qemu/docs/system/devices/
H A Divshmem.rst1 Inter-VM Shared Memory device
4 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:
[all …]
/openbmc/qemu/include/qemu/
H A Dmemalign.h2 * Allocation and free functions for aligned memory
12 * qemu_try_memalign: Allocate aligned memory
16 * Allocate memory on an aligned boundary (i.e. the returned
19 * On success, returns allocated memory; on failure, returns NULL.
21 * The memory allocated through this function must be freed via
26 * qemu_memalign: Allocate aligned memory, without failing
30 * Allocate memory in the same way as qemu_try_memalign(), but
31 * abort() with an error message if the memory allocation fails.
33 * The memory allocated through this function must be freed via
38 * qemu_vfree: Free memory allocated through qemu_memalign
[all …]
/openbmc/docs/designs/
H A Decc-dbus-sel.md9 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
19 correctable or ECC/other uncorrectable and whether ECC/other correctable memory
21 format and creates BMC memory ECC event log.
25 Therefore, the memory ECC information will be registered to D-Bus and generate
26 memory ECC SEL as well.
41 ECC-enabled memory controllers can detect and correct errors in operating
43 detection and correction of memory errors, which helps identify problems before
44 they become catastrophic faulty memory module.
[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/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/qemu/include/system/
H A Dmemory.h2 * Physical memory management API
35 #define TYPE_MEMORY_REGION "memory-region"
39 #define TYPE_IOMMU_MEMORY_REGION "iommu-memory-region"
235 /* RAM is a persistent kind memory */
249 * set, the OS will do the reservation, if supported for the memory type.
291 * Memory region callbacks
294 /* Read from the memory region. @addr is relative to @mr; @size is
299 /* Write to the memory region. @addr is relative to @mr; @size is
370 * to handle requests to the memory region. Other methods are optional.
378 * to an output TLB entry. If the IOMMU is aware of memory transaction
[all …]

12345678910>>...168