Directory Files
.. 2
File Size
Kconfig 4.3 kB
Makefile 952 B
badrange.c 7.9 kB
blk.c 8.2 kB
btt.c 44 kB
btt.h 7.4 kB
btt_devs.c 9.1 kB
bus.c 32 kB
claim.c 7.8 kB
core.c 14 kB
dax_devs.c 2.9 kB
dimm.c 3.1 kB
dimm_devs.c 26 kB
e820.c 1.9 kB
label.c 38 kB
label.h 4.1 kB
libnvdimm.mod.c 0 B
namespace_devs.c 68 kB
nd-core.h 7.9 kB
nd.h 15 kB
nd_blk.mod.c 0 B
nd_btt.mod.c 0 B
nd_e820.mod.c 0 B
nd_pmem.mod.c 0 B
nd_virtio.c 3.7 kB
nd_virtio.mod.c 0 B
of_pmem.c 2.7 kB
of_pmem.mod.c 0 B
pfn.h 1.5 kB
pfn_devs.c 22 kB
pmem.c 17 kB
pmem.h 1.2 kB
region.c 4.2 kB
region_devs.c 34 kB
security.c 14 kB
virtio_pmem.c 3.0 kB
virtio_pmem.h 1.3 kB
virtio_pmem.mod.c 0 B

Linux v5.15-rc6 - nvdimm

# SPDX-License-Identifier: GPL-2.0-only
menuconfig LIBNVDIMM
	tristate "NVDIMM (Non-Volatile Memory Device) Support"
	depends on PHYS_ADDR_T_64BIT
	depends on HAS_IOMEM
	depends on BLK_DEV
	  Generic support for non-volatile memory devices including
	  ACPI-6-NFIT defined resources.  On platforms that define an
	  NFIT, or otherwise can discover NVDIMM resources, a libnvdimm
	  bus is registered to advertise PMEM (persistent memory)
	  namespaces (/dev/pmemX) and BLK (sliding mmio window(s))
	  namespaces (/dev/ndblkX.Y). A PMEM namespace refers to a
	  memory resource that may span multiple DIMMs and support DAX
	  (see CONFIG_DAX).  A BLK namespace refers to an NVDIMM control
	  region which exposes an mmio register set for windowed access
	  mode to non-volatile memory.


	tristate "PMEM: Persistent memory block device support"
	default LIBNVDIMM
	select DAX_DRIVER
	select ND_BTT if BTT
	select ND_PFN if NVDIMM_PFN
	  Memory ranges for PMEM are described by either an NFIT
	  (NVDIMM Firmware Interface Table, see CONFIG_NFIT_ACPI), a
	  non-standard OEM-specific E820 memory type (type-12, see
	  CONFIG_X86_PMEM_LEGACY), or it is manually specified by the
	  'memmap=nn[KMG]!ss[KMG]' kernel command line (see
	  Documentation/admin-guide/kernel-parameters.rst).  This driver converts
	  these persistent memory ranges into block devices that are
	  capable of DAX (direct-access) file system mappings.  See
	  Documentation/driver-api/nvdimm/nvdimm.rst for more details.

	  Say Y if you want to use an NVDIMM

config ND_BLK
	tristate "BLK: Block data window (aperture) device support"
	default LIBNVDIMM
	select ND_BTT if BTT
	  Support NVDIMMs, or other devices, that implement a BLK-mode
	  access capability.  BLK-mode access uses memory-mapped-i/o
	  apertures to access persistent media.

	  Say Y if your platform firmware emits an ACPI.NFIT table
	  (CONFIG_ACPI_NFIT), or otherwise exposes BLK-mode

config ND_CLAIM

config ND_BTT

config BTT
	bool "BTT: Block Translation Table (atomic sector updates)"
	default y if LIBNVDIMM
	select ND_CLAIM
	  The Block Translation Table (BTT) provides atomic sector
	  update semantics for persistent memory devices, so that
	  applications that rely on sector writes not being torn (a
	  guarantee that typical disks provide) can continue to do so.
	  The BTT manifests itself as an alternate personality for an
	  NVDIMM namespace, i.e. a namespace can be in raw mode (pmemX,
	  ndblkX.Y, etc...), or 'sectored' mode, (pmemXs, ndblkX.Ys,

	  Select Y if unsure

config ND_PFN

	bool "PFN: Map persistent (device) memory"
	default LIBNVDIMM
	depends on ZONE_DEVICE
	select ND_CLAIM
	  Map persistent memory, i.e. advertise it to the memory
	  management sub-system.  By default persistent memory does
	  not support direct I/O, RDMA, or any other usage that
	  requires a 'struct page' to mediate an I/O request.  This
	  driver allocates and initializes the infrastructure needed
	  to support those use cases.

	  Select Y if unsure

	bool "NVDIMM DAX: Raw access to persistent memory"
	default LIBNVDIMM
	depends on NVDIMM_PFN
	  Support raw device dax access to a persistent memory
	  namespace.  For environments that want to hard partition
	  persistent memory, this capability provides a mechanism to
	  sub-divide a namespace into character devices that can only be
	  accessed via DAX (mmap(2)).

	  Select Y if unsure

config OF_PMEM
	tristate "Device-tree support for persistent memory regions"
	depends on OF
	default LIBNVDIMM
	  Allows regions of persistent memory to be described in the

	  Select Y if unsure.

	def_bool y
	depends on ENCRYPTED_KEYS

	tristate "Build the unit test core"
	depends on m
	depends on COMPILE_TEST && X86_64
	default m if COMPILE_TEST
	  Build the core of the unit test infrastructure. The result of
	  this build is non-functional for unit test execution, but it
	  otherwise helps catch build errors induced by changes to the
	  core devm_memremap_pages() implementation and other