[bug]Fix namespace section padding relative to other regions

Bug #1823595 reported by quanxian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
intel
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Description:

Commit cfe30b872058 "libnvdimm, pmem: adjust for section collisions with
'System RAM'" enabled the libnvdimm core 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

Commits:
ae86cbfef381 libnvdimm, pfn: Pad pfn namespaces relative to other regions
e3f5df762d4a tools/testing/nvdimm: Align test resources to 128M

Target Release: 19.04
Target Kernel: 5.0

Revision history for this message
quanxian (quanxian-wang) wrote :

should have been into 5.0 kernel

Changed in intel:
status: New → Fix Committed
Revision history for this message
quanxian (quanxian-wang) wrote :

ae86cbfef381 e3f5df762d4a

Changed in intel:
status: Fix Committed → Fix Released
Changed in linux (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.