arm64: ptdump: Discover start of vmemmap region at runtime

We will soon reclaim the part of the vmemmap region that covers VA space
that is not addressable by the hardware. To avoid confusion, ensure that
the 'vmemmap start' marker points at the start of the region that is
actually being used for the struct page array, rather than the start of
the region we set aside for it at build time.

Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Link: https://lore.kernel.org/r/20231213084024.2367360-13-ardb@google.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Acked-by: Mark Rutland <mark.rutland@arm.com>

diff --git a/arch/arm64/mm/ptdump.c b/arch/arm64/mm/ptdump.c
index 66ccb8d6997e8b0f2aab0517f040524ac3bac3d5..5f0849528ccf168eac4bfba112438023251c4103 100644 (file)
--- a/arch/arm64/mm/ptdump.c
+++ b/arch/arm64/mm/ptdump.c
@@ -346,6 +346,8 @@ void ptdump_check_wx(void)
 
 static int __init ptdump_init(void)
 {
+       u64 page_offset = _PAGE_OFFSET(vabits_actual);
+       u64 vmemmap_start = (u64)virt_to_page((void *)page_offset);
        struct addr_marker m[] = {
                { PAGE_OFFSET,          "Linear Mapping start" },
                { PAGE_END,             "Linear Mapping end" },
@@ -357,7 +359,7 @@ static int __init ptdump_init(void)
                { MODULES_END,          "Modules end" },
                { VMALLOC_START,        "vmalloc() area" },
                { VMALLOC_END,          "vmalloc() end" },
-               { VMEMMAP_START,        "vmemmap start" },
+               { vmemmap_start,        "vmemmap start" },
                { VMEMMAP_END,          "vmemmap end" },
                { PCI_IO_START,         "PCI I/O start" },
                { PCI_IO_END,           "PCI I/O end" },