summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/armada-xp-gp.dts
diff options
context:
space:
mode:
authorArd Biesheuvel <ard.biesheuvel@linaro.org>2016-03-08 21:09:29 +0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-03-16 08:42:57 -0700
commit97142f3009557c27091c694f927041f28ef81573 (patch)
tree061c459ac1c3e90833b4b125644e969fccb7c427 /arch/arm/boot/dts/armada-xp-gp.dts
parent62e21959dc6f25c5fce0c1a0934e4a9d982bf99b (diff)
arm64: account for sparsemem section alignment when choosing vmemmap offset
commit 36e5cd6b897e17d03008f81e075625d8e43e52d0 upstream. Commit dfd55ad85e4a ("arm64: vmemmap: use virtual projection of linear region") fixed an issue where the struct page array would overflow into the adjacent virtual memory region if system RAM was placed so high up in physical memory that its addresses were not representable in the build time configured virtual address size. However, the fix failed to take into account that the vmemmap region needs to be relatively aligned with respect to the sparsemem section size, so that a sequence of page structs corresponding with a sparsemem section in the linear region appears naturally aligned in the vmemmap region. So round up vmemmap to sparsemem section size. Since this essentially moves the projection of the linear region up in memory, also revert the reduction of the size of the vmemmap region. Fixes: dfd55ad85e4a ("arm64: vmemmap: use virtual projection of linear region") Tested-by: Mark Langsdorf <mlangsdo@redhat.com> Tested-by: David Daney <david.daney@cavium.com> Tested-by: Robert Richter <rrichter@cavium.com> Acked-by: Catalin Marinas <catalin.marinas@arm.com> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Signed-off-by: Will Deacon <will.deacon@arm.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/arm/boot/dts/armada-xp-gp.dts')
0 files changed, 0 insertions, 0 deletions