On 12/08/2016 08:39 AM, Jérôme Glisse wrote: > Architecture that wish to support un-addressable device memory should make > sure to never populate the kernel linar mapping for the physical range.
Does the platform somehow provide a range of physical addresses for this unaddressable area? How do we know no memory will be hot-added in a range we're using for unaddressable device memory, for instance?
