On 9/21/23 04:37, Bjorn Andersson wrote:
In some configurations, the exact placement of the rmtfs shared memory region isn't so strict. The DeviceTree author can then choose to use the "size" property and rely on the OS for placement (in combination with "alloc-ranges", if desired). But on some platforms the rmtfs memory region may not be allocated adjacent to regions allocated by other clients. Add support for discarding the first and last 4k block in the region, if qcom,use-guard-pages is specified in DeviceTree. Signed-off-by: Bjorn Andersson <quic_bjorande@xxxxxxxxxxx> ---
I don't want to block this anymore, but I guess I should ask the question whether it would be valuable to add a common reserved-memory property for e.g. low-padding and high-padding Have we seen cases of that outside rmtfs? Konrad
