diff options
| author | Dan Williams <dan.j.williams@intel.com> | 2019-11-07 04:43:43 +0300 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2019-11-07 17:45:00 +0300 |
| commit | a6c7f4c6aea5f4ca6056b06cec7ebd79f8c23e33 (patch) | |
| tree | c942e9a1b25e2cf4b47a233ef22e4badebcd86c7 /include/linux/memregion.h | |
| parent | 460370ab20b6cc174256e46e192adf01e730faf6 (diff) | |
| download | linux-a6c7f4c6aea5f4ca6056b06cec7ebd79f8c23e33.tar.xz | |
device-dax: Add a driver for "hmem" devices
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>
Diffstat (limited to 'include/linux/memregion.h')
| -rw-r--r-- | include/linux/memregion.h | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/include/linux/memregion.h b/include/linux/memregion.h index 7de7c0a1444e..e11595256cac 100644 --- a/include/linux/memregion.h +++ b/include/linux/memregion.h @@ -4,6 +4,10 @@ #include <linux/types.h> #include <linux/errno.h> +struct memregion_info { + int target_node; +}; + #ifdef CONFIG_MEMREGION int memregion_alloc(gfp_t gfp); void memregion_free(int id); |