blob: ace25b53b7556530a4191e0eae803ce76635317e [file] [log] [blame]
Dan Williams18da2c92015-06-09 14:13:37 -04001menuconfig LIBNVDIMM
Dan Williamsb94d5232015-05-19 22:54:31 -04002 tristate "NVDIMM (Non-Volatile Memory Device) Support"
3 depends on PHYS_ADDR_T_64BIT
4 depends on BLK_DEV
5 help
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))
Vishal Verma5212e112015-06-25 04:20:32 -040011 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.
Dan Williams18da2c92015-06-09 14:13:37 -040016
17if LIBNVDIMM
18
19config BLK_DEV_PMEM
20 tristate "PMEM: Persistent memory block device support"
21 default LIBNVDIMM
22 depends on HAS_IOMEM
Vishal Verma5212e112015-06-25 04:20:32 -040023 select ND_BTT if BTT
Dan Williamse1455742015-07-30 17:57:47 -040024 select ND_PFN if NVDIMM_PFN
Dan Williams18da2c92015-06-09 14:13:37 -040025 help
26 Memory ranges for PMEM are described by either an NFIT
27 (NVDIMM Firmware Interface Table, see CONFIG_NFIT_ACPI), a
28 non-standard OEM-specific E820 memory type (type-12, see
29 CONFIG_X86_PMEM_LEGACY), or it is manually specified by the
30 'memmap=nn[KMG]!ss[KMG]' kernel command line (see
31 Documentation/kernel-parameters.txt). This driver converts
32 these persistent memory ranges into block devices that are
33 capable of DAX (direct-access) file system mappings. See
34 Documentation/nvdimm/nvdimm.txt for more details.
35
36 Say Y if you want to use an NVDIMM
37
Ross Zwisler047fc8a2015-06-25 04:21:02 -040038config ND_BLK
39 tristate "BLK: Block data window (aperture) device support"
40 default LIBNVDIMM
41 select ND_BTT if BTT
42 help
43 Support NVDIMMs, or other devices, that implement a BLK-mode
44 access capability. BLK-mode access uses memory-mapped-i/o
45 apertures to access persistent media.
46
47 Say Y if your platform firmware emits an ACPI.NFIT table
48 (CONFIG_ACPI_NFIT), or otherwise exposes BLK-mode
49 capabilities.
50
Dan Williamse1455742015-07-30 17:57:47 -040051config ND_CLAIM
52 bool
53
Vishal Verma5212e112015-06-25 04:20:32 -040054config ND_BTT
55 tristate
56
Dan Williams8c2f7e82015-06-25 04:20:04 -040057config BTT
Vishal Verma5212e112015-06-25 04:20:32 -040058 bool "BTT: Block Translation Table (atomic sector updates)"
59 default y if LIBNVDIMM
Dan Williamse1455742015-07-30 17:57:47 -040060 select ND_CLAIM
Vishal Verma5212e112015-06-25 04:20:32 -040061 help
62 The Block Translation Table (BTT) provides atomic sector
63 update semantics for persistent memory devices, so that
64 applications that rely on sector writes not being torn (a
65 guarantee that typical disks provide) can continue to do so.
66 The BTT manifests itself as an alternate personality for an
67 NVDIMM namespace, i.e. a namespace can be in raw mode (pmemX,
68 ndblkX.Y, etc...), or 'sectored' mode, (pmemXs, ndblkX.Ys,
69 etc...).
70
71 Select Y if unsure
Dan Williams8c2f7e82015-06-25 04:20:04 -040072
Dan Williamse1455742015-07-30 17:57:47 -040073config ND_PFN
74 tristate
75
76config NVDIMM_PFN
77 bool "PFN: Map persistent (device) memory"
78 default LIBNVDIMM
79 select ND_CLAIM
80 help
81 Map persistent memory, i.e. advertise it to the memory
82 management sub-system. By default persistent memory does
83 not support direct I/O, RDMA, or any other usage that
84 requires a 'struct page' to mediate an I/O request. This
85 driver allocates and initializes the infrastructure needed
86 to support those use cases.
87
88 Select Y if unsure
89
Dan Williams18da2c92015-06-09 14:13:37 -040090endif