a6c7f4c6ae
Platform firmware like EFI/ACPI may publish "hmem" platform devices. Such a device is a performance differentiated memory range likely reserved for an application specific use case. The driver gives access to 100% of the capacity via a device-dax mmap instance by default. However, if over-subscription and other kernel memory management is desired the resulting dax device can be assigned to the core-mm via the kmem driver. This consumes "hmem" devices the producer of "hmem" devices is saved for a follow-on patch so that it can reference the new CONFIG_DEV_DAX_HMEM symbol to gate performing the enumeration work. Reported-by: kbuild test robot <lkp@intel.com> Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> Acked-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
13 lines
273 B
Makefile
13 lines
273 B
Makefile
# SPDX-License-Identifier: GPL-2.0
|
|
obj-$(CONFIG_DAX) += dax.o
|
|
obj-$(CONFIG_DEV_DAX) += device_dax.o
|
|
obj-$(CONFIG_DEV_DAX_KMEM) += kmem.o
|
|
obj-$(CONFIG_DEV_DAX_HMEM) += dax_hmem.o
|
|
|
|
dax-y := super.o
|
|
dax-y += bus.o
|
|
device_dax-y := device.o
|
|
dax_hmem-y := hmem.o
|
|
|
|
obj-y += pmem/
|