diff options
| author | Dan Williams <dan.j.williams@intel.com> | 2015-08-24 19:20:23 -0400 |
|---|---|---|
| committer | Dan Williams <dan.j.williams@intel.com> | 2015-08-28 23:40:05 -0400 |
| commit | 004f1afbe199e6ab20805b95aefd83ccd24bc5c7 (patch) | |
| tree | 4c7df96fc10599da6f31639a1835a8ada97ef2d8 /drivers/acpi/Kconfig | |
| parent | 32ab0a3f51701cb37ab960635254d5f84ec3de0a (diff) | |
| download | linux-stable-004f1afbe199e6ab20805b95aefd83ccd24bc5c7.tar.gz linux-stable-004f1afbe199e6ab20805b95aefd83ccd24bc5c7.tar.bz2 linux-stable-004f1afbe199e6ab20805b95aefd83ccd24bc5c7.zip | |
libnvdimm, pmem: direct map legacy pmem by default
The expectation is that the legacy / non-standard pmem discovery method
(e820 type-12) will only ever be used to describe small quantities of
persistent memory. Larger capacities will be described via the ACPI
NFIT. When "allocate struct page from pmem" support is added this default
policy can be overridden by assigning a legacy pmem namespace to a pfn
device, however this would be only be necessary if a platform used the
legacy mechanism to define a very large range.
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'drivers/acpi/Kconfig')
0 files changed, 0 insertions, 0 deletions