| /openbmc/linux/tools/testing/selftests/memory-hotplug/ |
| D | mem-on-off-test.sh | |
| /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
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/qemu/include/hw/mem/ |
| H A D | memory-device.h | 2 * 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/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | Memory_v1.xml | 4 <!--# 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 D | Memory_v1.xml | 4 <!--# 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/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | Dimm.interface.yaml | 7 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 D | PersistentMemory.interface.yaml | 2 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/linux/Documentation/devicetree/bindings/memory-controllers/fsl/ |
| D | fsl,ddr.yaml | |
| /openbmc/linux/Documentation/mm/ |
| D | memory-model.rst | |
| D | numa.rst | |
| /openbmc/linux/Documentation/admin-guide/mm/ |
| D | concepts.rst | |
| D | numaperf.rst | |
| /openbmc/linux/Documentation/arch/arm64/ |
| D | kdump.rst | |
| /openbmc/linux/Documentation/core-api/ |
| D | memory-hotplug.rst | |
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Memory.v1_21_0.json | 2 "$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/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Memory.v1_21_0.json | 2 "$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 D | MemoryRegion.v1_0_3.json | 36 "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 D | MemoryChunks.v1_6_2.json | 42 "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 D | MemoryMetrics.v1_7_3.json | 39 …"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 …]
|
| /openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ |
| D | memory.json | |
| /openbmc/qemu/docs/ |
| H A D | memory-hotplug.txt | 1 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/linux/drivers/memory/tegra/ |
| D | Kconfig | |
| /openbmc/linux/tools/testing/selftests/cgroup/ |
| D | test_memcontrol.c | |
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| D | dev-mem2mem.rst | |
| /openbmc/linux/tools/testing/selftests/arm64/mte/ |
| D | check_mmap_options.c | |