Kconfig 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. menuconfig DAX
  3. tristate "DAX: direct access to differentiated memory"
  4. default m if NVDIMM_DAX
  5. if DAX
  6. config DEV_DAX
  7. tristate "Device DAX: direct access mapping device"
  8. depends on TRANSPARENT_HUGEPAGE
  9. help
  10. Support raw access to differentiated (persistence, bandwidth,
  11. latency...) memory via an mmap(2) capable character
  12. device. Platform firmware or a device driver may identify a
  13. platform memory resource that is differentiated from the
  14. baseline memory pool. Mappings of a /dev/daxX.Y device impose
  15. restrictions that make the mapping behavior deterministic.
  16. config DEV_DAX_PMEM
  17. tristate "PMEM DAX: direct access to persistent memory"
  18. depends on LIBNVDIMM && NVDIMM_DAX && DEV_DAX
  19. default DEV_DAX
  20. help
  21. Support raw access to persistent memory. Note that this
  22. driver consumes memory ranges allocated and exported by the
  23. libnvdimm sub-system.
  24. Say M if unsure
  25. config DEV_DAX_HMEM
  26. tristate "HMEM DAX: direct access to 'specific purpose' memory"
  27. depends on EFI_SOFT_RESERVE
  28. select NUMA_KEEP_MEMINFO if NUMA_MEMBLKS
  29. default DEV_DAX
  30. help
  31. EFI 2.8 platforms, and others, may advertise 'specific purpose'
  32. memory. For example, a high bandwidth memory pool. The
  33. indication from platform firmware is meant to reserve the
  34. memory from typical usage by default. This driver creates
  35. device-dax instances for these memory ranges, and that also
  36. enables the possibility to assign them to the DEV_DAX_KMEM
  37. driver to override the reservation and add them to kernel
  38. "System RAM" pool.
  39. Say M if unsure.
  40. config DEV_DAX_CXL
  41. tristate "CXL DAX: direct access to CXL RAM regions"
  42. depends on CXL_BUS && CXL_REGION && DEV_DAX
  43. default CXL_REGION && DEV_DAX
  44. help
  45. CXL RAM regions are either mapped by platform-firmware
  46. and published in the initial system-memory map as "System RAM", mapped
  47. by platform-firmware as "Soft Reserved", or dynamically provisioned
  48. after boot by the CXL driver. In the latter two cases a device-dax
  49. instance is created to access that unmapped-by-default address range.
  50. Per usual it can remain as dedicated access via a device interface, or
  51. converted to "System RAM" via the dax_kmem facility.
  52. config DEV_DAX_HMEM_DEVICES
  53. depends on DEV_DAX_HMEM && DAX
  54. def_bool y
  55. config DEV_DAX_KMEM
  56. tristate "KMEM DAX: map dax-devices as System-RAM"
  57. default DEV_DAX
  58. depends on DEV_DAX
  59. depends on MEMORY_HOTPLUG # for add_memory() and friends
  60. help
  61. Support access to persistent, or other performance
  62. differentiated memory as if it were System RAM. This allows
  63. easier use of persistent memory by unmodified applications, or
  64. adds core kernel memory services to heterogeneous memory types
  65. (HMEM) marked "reserved" by platform firmware.
  66. To use this feature, a DAX device must be unbound from the
  67. device_dax driver and bound to this kmem driver on each boot.
  68. Say N if unsure.
  69. endif