On October 6, 2025 thus sayeth Anshul Dalal: > With the memory map configuration being done dynamically, reserve extra > space during U-Boot relocation to ensure we have enough for the fixups. > > Signed-off-by: Anshul Dalal <[email protected]> > --- > arch/arm/mach-k3/arm64/arm64-mmu.c | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/arch/arm/mach-k3/arm64/arm64-mmu.c > b/arch/arm/mach-k3/arm64/arm64-mmu.c > index 479451452a2..f999af143fb 100644 > --- a/arch/arm/mach-k3/arm64/arm64-mmu.c > +++ b/arch/arm/mach-k3/arm64/arm64-mmu.c > @@ -41,3 +41,8 @@ struct mm_region k3_mem_map[K3_MEM_MAP_LEN] = { > }; > > struct mm_region *mem_map = k3_mem_map; > + > +u64 get_page_table_size(void) > +{ > + return SZ_128K; > +}
How are we calculating this size? With 2^39 addresses this should bring us into the MBs of TLB data. I see we limit U-Boot to 512 entries, but that doesn't match this either ~Bryan
