[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <162398829836.1363949.3616148004557919453.b4-ty@ellerman.id.au>
Date: Fri, 18 Jun 2021 13:51:38 +1000
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Christophe Leroy <christophe.leroy@...roup.eu>
Cc: linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] powerpc/32: Display modules range in virtual memory layout
On Fri, 11 Jun 2021 19:08:54 +0000 (UTC), Christophe Leroy wrote:
> book3s/32 and 8xx don't use vmalloc for modules.
>
> Print the modules area at startup as part of the virtual memory layout:
>
> [ 0.000000] Kernel virtual memory layout:
> [ 0.000000] * 0xffafc000..0xffffc000 : fixmap
> [ 0.000000] * 0xc9000000..0xffafc000 : vmalloc & ioremap
> [ 0.000000] * 0xb0000000..0xc0000000 : modules
> [ 0.000000] Memory: 118480K/131072K available (7152K kernel code, 2320K rwdata, 1328K rodata, 368K init, 854K bss, 12592K reserved, 0K cma-reserved)
Applied to powerpc/next.
[1/1] powerpc/32: Display modules range in virtual memory layout
https://git.kernel.org/powerpc/c/baf24d23be7d2357a2aa9c5ffb6a2d680ac2a68c
cheers
Powered by blists - more mailing lists