arm64: ignore memory outside of the linear range
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 of 2 patches 0 repliesNew
1 of 2 patches is in this archive. The cover letter announces 2.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 2/2 | arm64: set MAX_MEMBLOCK_ADDR according to linear region size | +0 | 11 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] arm64: ignore memory outside of the linear range
Quoted 20 lines · Ard Biesheuvel
Quoted 20 lines
Quoted 19 lines
This is a followup to the single patch I posted on Aug 15th to ignore RAM that cannot be covered by the linear mapping. Instead of clipping the memory after the fact, this clips the memory before installing the regions into the memblock memory table.
This is basically the approach that Mark Rutland suggested here
http://article.gmane.org/gmane.linux.ports.arm.kernel/430239
but modified to correctly consider the base of the kernel image as the start of the linear mapping.
Ard Biesheuvel (2):
of/fdt: make memblock maximum physical address arch configurable
arm64: setMAX_MEMBLOCK_ADDRaccording to linear region sizearch/arm64/include/asm/memory.h | 8 ++++++++ drivers/of/fdt.c | 12 +++++++----- 2 files changed, 15 insertions(+), 5 deletions(-)
Quoted 8 lines
Quoted 5 lines
Tested on Freescale LS2085ARDB which has a split memory region that triggers the bug.
Tested-by Stuart Yoder <[email protected]>Will you be picking up this series for v4.3? If so, do you need me to resend it with the tags added?
Sorry, I missed Rob's ack on the of/fdt.c change. I'll pick these up later today, no need to resend.
Cheers,
Will