diff options
| author | Dan Williams | 2018-11-24 19:47:04 +0100 |
|---|---|---|
| committer | Dan Williams | 2018-12-05 23:16:12 +0100 |
| commit | ae86cbfef3818300f1972e52f67a93211acb0e24 (patch) | |
| tree | b36ab8d85a1cbcb9344a0bb29e1d0f18eef23a6b /drivers/acpi | |
| parent | tools/testing/nvdimm: Align test resources to 128M (diff) | |
| download | kernel-qcow2-linux-ae86cbfef3818300f1972e52f67a93211acb0e24.tar.gz kernel-qcow2-linux-ae86cbfef3818300f1972e52f67a93211acb0e24.tar.xz kernel-qcow2-linux-ae86cbfef3818300f1972e52f67a93211acb0e24.zip | |
libnvdimm, pfn: Pad pfn namespaces relative to other regions
Commit cfe30b872058 "libnvdimm, pmem: adjust for section collisions with
'System RAM'" enabled Linux to workaround occasions where platform
firmware arranges for "System RAM" and "Persistent Memory" to collide
within a single section boundary. Unfortunately, as reported in this
issue [1], platform firmware can inflict the same collision between
persistent memory regions.
The approach of interrogating iomem_resource does not work in this
case because platform firmware may merge multiple regions into a single
iomem_resource range. Instead provide a method to interrogate regions
that share the same parent bus.
This is a stop-gap until the core-MM can grow support for hotplug on
sub-section boundaries.
[1]: https://github.com/pmem/ndctl/issues/76
Fixes: cfe30b872058 ("libnvdimm, pmem: adjust for section collisions with...")
Cc: <stable@vger.kernel.org>
Reported-by: Patrick Geary <patrickg@supermicro.com>
Tested-by: Patrick Geary <patrickg@supermicro.com>
Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Diffstat (limited to 'drivers/acpi')
0 files changed, 0 insertions, 0 deletions