Skip to content

arm64: ignore memory outside of the linear range

Will Deacon linux-arm-kernel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 2 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 2 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] arm64: ignore memory outside of the linear range
Quoted 27 lines · Stuart Yoder
Quoted 27 lines · Ard Biesheuvel
Quoted 26 lines
Quoted 25 lines
Quoted 12 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.

Quoted 7 lines

Ard Biesheuvel (2):
of/fdt: make memblock maximum physical address arch configurable
arm64: set MAX_MEMBLOCK_ADDR according to linear region size

 arch/arm64/include/asm/memory.h |  8 ++++++++
 drivers/of/fdt.c                | 12 +++++++-----
 2 files changed, 15 insertions(+), 5 deletions(-)

Tested on Freescale LS2085ARDB which has a split memory region that triggers the bug.

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

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.

Are we sending to stable as well?

I've already pushed the patch out without a Cc stable (it's not a regression afaict), so if you want it backported then you'll need to send it to stable separately.

Will