| /openbmc/linux/Documentation/driver-api/nvdimm/ |
| H A D | nvdimm.rst | 17 LIBNVDIMM PMEM
18 PMEM-REGIONs, Atomic Sectors, and DAX
49 PMEM:
51 block device composed of PMEM is capable of DAX. A PMEM address range
63 mmap persistent memory, from a PMEM block device, directly into a
78 table with atomic update semantics to front a PMEM block device
124 LIBNVDIMM PMEM
131 specification standardizes not only the description of PMEM, but also
142 the PMEM range. In contrast ND_NAMESPACE_IO ranges, once registered,
146 PMEM-REGIONs, Atomic Sectors, and DAX
[all …]
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | memory_chunks.hpp | 11 PMEM, enumerator
31 {AddressRangeType::PMEM, "PMEM"},
|
| H A D | memory.hpp | 107 PMEM, enumerator
210 {OperatingMemoryModes::PMEM, "PMEM"},
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | papr_hcalls.rst | 228 (described in table below) of the PMEM device and health-bit-valid-bitmap indicate
238 | 00 | PMEM device is unable to persist memory contents. |
241 | 01 | PMEM device failed to persist memory contents. Either contents were |
245 | 02 | PMEM device contents are persisted from previous IPL. The data from |
248 | 03 | PMEM device contents are not persisted from previous IPL. There was no|
251 | 04 | PMEM device memory life remaining is critically low |
253 | 05 | PMEM device will be garded off next IPL due to failure |
255 | 06 | PMEM device contents cannot persist due to current platform health |
259 | 07 | PMEM device is unable to persist memory contents in certain conditions|
261 | 08 | PMEM device is encrypted |
[all …]
|
| /openbmc/u-boot/arch/x86/include/asm/arch-quark/acpi/ |
| H A D | southcluster.asl | 119 0x00000000, , , PMEM)
125 CreateDwordField(MCRS, ^PMEM._MIN, PMIN)
126 CreateDwordField(MCRS, ^PMEM._MAX, PMAX)
127 CreateDwordField(MCRS, ^PMEM._LEN, PLEN)
|
| /openbmc/u-boot/arch/x86/include/asm/arch-baytrail/acpi/ |
| H A D | southcluster.asl | 122 0x00000000, , , PMEM)
134 CreateDwordField(MCRS, ^PMEM._MIN, PMIN)
135 CreateDwordField(MCRS, ^PMEM._MAX, PMAX)
136 CreateDwordField(MCRS, ^PMEM._LEN, PLEN)
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/ndctl/ |
| H A D | ndctl_v79.bb | 5 NVDIMMs, namely,PMEM, BLK, and NVDIMM devices that can \
6 simultaneously support both PMEM and BLK mode access."
|
| /openbmc/linux/drivers/nvdimm/ |
| H A D | Kconfig | 12 bus is registered to advertise PMEM (persistent memory)
13 namespaces (/dev/pmemX). A PMEM namespace refers to a
20 tristate "PMEM: Persistent memory block device support"
26 Memory ranges for PMEM are described by either an NFIT
|
| /openbmc/linux/drivers/dax/ |
| H A D | Kconfig | 20 tristate "PMEM DAX: direct access to persistent memory"
|
| /openbmc/linux/Documentation/driver-api/cxl/ |
| H A D | memory-devices.rst | 253 example mem3 can participate in one or more of a PMEM interleave that spans to
254 Host Bridges, a PMEM interleave that targets a single Host Bridge, a Volatile
|
| /openbmc/linux/arch/powerpc/perf/ |
| H A D | isa207-common.c | 238 ret |= P(LVL, HIT) | LEVEL(PMEM); in isa207_find_source()
242 ret |= P(LVL, HIT) | LEVEL(PMEM) | REM; in isa207_find_source()
|
| /openbmc/u-boot/arch/x86/include/asm/arch-tangier/acpi/ |
| H A D | southcluster.asl | 61 0x80000000, , , PMEM)
|
| /openbmc/linux/drivers/cxl/ |
| H A D | Kconfig | 72 tristate "CXL PMEM: Persistent Memory Support"
|
| /openbmc/linux/Documentation/mm/ |
| H A D | physical_memory.rst | 71 * ``ZONE_DEVICE`` represents memory residing on devices such as PMEM and GPU.
|
| /openbmc/linux/arch/x86/events/amd/ |
| H A D | ibs.c | 751 [IBS_DATA_SRC_EXT_PMEM] = LN(PMEM),
|
| /openbmc/linux/arch/x86/events/intel/ |
| H A D | ds.c | 108 u64 pmem_or_l4 = pmem ? LEVEL(PMEM) : LEVEL(L4); in __intel_pmu_pebs_data_source_skl()
|
| /openbmc/linux/Documentation/admin-guide/sysctl/ |
| H A D | kernel.rst | 702 A rule of thumb is to set this to less than 1/10 of the PMEM node
|
| /openbmc/linux/ |
| H A D | MAINTAINERS | 12050 LIBNVDIMM PMEM: PERSISTENT MEMORY DRIVER
22948 VIRTIO PMEM DRIVER
|