2 tristate "NVDIMM (Non-Volatile Memory Device) Support"
3 depends on PHYS_ADDR_T_64BIT
6 Generic support for non-volatile memory devices including
7 ACPI-6-NFIT defined resources. On platforms that define an
8 NFIT, or otherwise can discover NVDIMM resources, a libnvdimm
9 bus is registered to advertise PMEM (persistent memory)
10 namespaces (/dev/pmemX) and BLK (sliding mmio window(s))
11 namespaces (/dev/ndblkX.Y). A PMEM namespace refers to a
12 memory resource that may span multiple DIMMs and support DAX
13 (see CONFIG_DAX). A BLK namespace refers to an NVDIMM control
14 region which exposes an mmio register set for windowed access
15 mode to non-volatile memory.
20 tristate "PMEM: Persistent memory block device support"
25 Memory ranges for PMEM are described by either an NFIT
26 (NVDIMM Firmware Interface Table, see CONFIG_NFIT_ACPI), a
27 non-standard OEM-specific E820 memory type (type-12, see
28 CONFIG_X86_PMEM_LEGACY), or it is manually specified by the
29 'memmap=nn[KMG]!ss[KMG]' kernel command line (see
30 Documentation/kernel-parameters.txt). This driver converts
31 these persistent memory ranges into block devices that are
32 capable of DAX (direct-access) file system mappings. See
33 Documentation/nvdimm/nvdimm.txt for more details.
35 Say Y if you want to use an NVDIMM
41 bool "BTT: Block Translation Table (atomic sector updates)"
42 default y if LIBNVDIMM
44 The Block Translation Table (BTT) provides atomic sector
45 update semantics for persistent memory devices, so that
46 applications that rely on sector writes not being torn (a
47 guarantee that typical disks provide) can continue to do so.
48 The BTT manifests itself as an alternate personality for an
49 NVDIMM namespace, i.e. a namespace can be in raw mode (pmemX,
50 ndblkX.Y, etc...), or 'sectored' mode, (pmemXs, ndblkX.Ys,