From: james.morse@arm•com (James Morse)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 3/3] arm64: mm: Restrictive printing for modules and PCI I/O in memory layout
Date: Mon, 18 Apr 2016 12:15:26 +0100 [thread overview]
Message-ID: <5714C1CE.4090307@arm.com> (raw)
In-Reply-To: <1460948988-7477-4-git-send-email-wangkefeng.wang@huawei.com>
On 18/04/16 04:09, Kefeng Wang wrote:
> The modules and PCI I/O informations in Virtual kernel memory layout
> are inappropriate when corresponding config is not enabled, so don't
> show them then.
I'm not sure about this, it looks like these areas are still reserved, so this
is still useful debug information. mm/dump.c will still print any mappings in
these ranges, its good to be consistent.
Thanks,
James
> ---
> arch/arm64/mm/init.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> index c96fe51..e06a445 100644
> --- a/arch/arm64/mm/init.c
> +++ b/arch/arm64/mm/init.c
> @@ -367,8 +367,10 @@ void __init mem_init(void)
> pr_cont(" kasan : 0x%16lx - 0x%16lx (%6ld GB)\n",
> MLG(KASAN_SHADOW_START, KASAN_SHADOW_END));
> #endif
> +#ifdef CONFIG_MODULES
> pr_cont(" modules : 0x%16lx - 0x%16lx (%6ld MB)\n",
> MLM(MODULES_VADDR, MODULES_END));
> +#endif
> pr_cont(" vmalloc : 0x%16lx - 0x%16lx (%6ld GB)\n",
> MLG(VMALLOC_START, VMALLOC_END));
> pr_cont(" .text : 0x%p" " - 0x%p" " (%6ld KB)\n",
> @@ -390,8 +392,10 @@ void __init mem_init(void)
> #endif
> pr_cont(" fixed : 0x%16lx - 0x%16lx (%6ld KB)\n",
> MLK(FIXADDR_START, FIXADDR_TOP));
> +#ifdef CONFIG_PCI
> pr_cont(" PCI I/O : 0x%16lx - 0x%16lx (%6ld MB)\n",
> MLM(PCI_IO_START, PCI_IO_END));
> +#endif
> pr_cont(" memory : 0x%16lx - 0x%16lx (%6ld MB)\n",
> MLM(__phys_to_virt(memblock_start_of_DRAM()),
> (unsigned long)high_memory));
>
next prev parent reply other threads:[~2016-04-18 11:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 7:49 [PATCH] arm64: mm: Enhance Virtual kernel memory layout Kefeng Wang
2016-04-13 9:26 ` James Morse
2016-04-14 6:57 ` Kefeng Wang
2016-04-15 17:20 ` Will Deacon
2016-04-18 2:05 ` Kefeng Wang
2016-04-18 3:09 ` [PATCH v2 0/3] " Kefeng Wang
2016-04-18 3:09 ` [PATCH v2 1/3] arm64: mm: make pr_cont() per line in " Kefeng Wang
2016-04-18 11:16 ` James Morse
2016-04-18 11:21 ` Ard Biesheuvel
2016-04-18 13:13 ` James Morse
2016-04-19 5:58 ` Kefeng Wang
2016-04-18 3:09 ` [PATCH v2 2/3] arm64: mm: Show bss segment in " Kefeng Wang
2016-04-18 11:14 ` James Morse
2016-04-18 3:09 ` [PATCH v2 3/3] arm64: mm: Restrictive printing for modules and PCI I/O in " Kefeng Wang
2016-04-18 11:15 ` James Morse [this message]
2016-04-19 7:08 ` Kefeng Wang
2016-05-12 12:16 ` [PATCH v3 0/2] arm64: mm: Enhance Virtual kernel " Kefeng Wang
2016-05-12 12:16 ` [PATCH v3 1/2] arm64: mm: make pr_cont() per line in " Kefeng Wang
2016-05-12 12:16 ` [PATCH v3 2/2] arm64: mm: Show bss segment in " Kefeng Wang
2016-05-12 13:36 ` [PATCH v3 0/2] arm64: mm: Enhance Virtual " Will Deacon
2016-05-13 1:21 ` Kefeng Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5714C1CE.4090307@arm.com \
--to=james.morse@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox