blob: 5fdf269a822e59faff72e0f3297a194909bc998a [file] [log] [blame]
Thomas Gleixnerec8f24b2019-05-19 13:07:45 +01001# SPDX-License-Identifier: GPL-2.0-only
Dan Williams7b6be842017-04-11 09:49:49 -07002menuconfig DAX
Dan Williamsab68f262016-05-18 09:15:08 -07003 tristate "DAX: direct access to differentiated memory"
Dan Williams956a4cd2017-04-07 16:42:08 -07004 select SRCU
Dan Williams7b6be842017-04-11 09:49:49 -07005 default m if NVDIMM_DAX
6
7if DAX
8
9config DEV_DAX
10 tristate "Device DAX: direct access mapping device"
11 depends on TRANSPARENT_HUGEPAGE
Dan Williamsab68f262016-05-18 09:15:08 -070012 help
13 Support raw access to differentiated (persistence, bandwidth,
14 latency...) memory via an mmap(2) capable character
15 device. Platform firmware or a device driver may identify a
16 platform memory resource that is differentiated from the
17 baseline memory pool. Mappings of a /dev/daxX.Y device impose
18 restrictions that make the mapping behavior deterministic.
19
Dan Williamsab68f262016-05-18 09:15:08 -070020config DEV_DAX_PMEM
21 tristate "PMEM DAX: direct access to persistent memory"
Mike Galbraith74d71a02017-05-06 06:14:43 +020022 depends on LIBNVDIMM && NVDIMM_DAX && DEV_DAX
Dan Williamsab68f262016-05-18 09:15:08 -070023 default DEV_DAX
24 help
25 Support raw access to persistent memory. Note that this
26 driver consumes memory ranges allocated and exported by the
27 libnvdimm sub-system.
28
Dan Williams730926c2017-07-16 13:51:53 -070029 Say M if unsure
30
Dan Williamsa6c7f4c2019-11-06 17:43:43 -080031config DEV_DAX_HMEM
32 tristate "HMEM DAX: direct access to 'specific purpose' memory"
33 depends on EFI_SOFT_RESERVE
Dan Williams5ccac542020-10-13 16:49:28 -070034 select NUMA_KEEP_MEMINFO if (NUMA && X86)
Dan Williamsa6c7f4c2019-11-06 17:43:43 -080035 default DEV_DAX
36 help
37 EFI 2.8 platforms, and others, may advertise 'specific purpose'
38 memory. For example, a high bandwidth memory pool. The
39 indication from platform firmware is meant to reserve the
40 memory from typical usage by default. This driver creates
41 device-dax instances for these memory ranges, and that also
42 enables the possibility to assign them to the DEV_DAX_KMEM
43 driver to override the reservation and add them to kernel
44 "System RAM" pool.
45
46 Say M if unsure.
47
Dan Williamsc01044c2020-10-13 16:49:13 -070048config DEV_DAX_HMEM_DEVICES
49 depends on DEV_DAX_HMEM && DAX=y
50 def_bool y
51
Dave Hansenc221c0b2019-02-25 10:57:40 -080052config DEV_DAX_KMEM
53 tristate "KMEM DAX: volatile-use of persistent memory"
54 default DEV_DAX
55 depends on DEV_DAX
56 depends on MEMORY_HOTPLUG # for add_memory() and friends
57 help
Dan Williamsa6c7f4c2019-11-06 17:43:43 -080058 Support access to persistent, or other performance
59 differentiated memory as if it were System RAM. This allows
60 easier use of persistent memory by unmodified applications, or
61 adds core kernel memory services to heterogeneous memory types
62 (HMEM) marked "reserved" by platform firmware.
Dave Hansenc221c0b2019-02-25 10:57:40 -080063
64 To use this feature, a DAX device must be unbound from the
Dan Williamsa6c7f4c2019-11-06 17:43:43 -080065 device_dax driver and bound to this kmem driver on each boot.
Dave Hansenc221c0b2019-02-25 10:57:40 -080066
67 Say N if unsure.
68
Dan Williamsab68f262016-05-18 09:15:08 -070069endif