From: Baoquan He <bhe@redhat.com>
To: Huang Shijie <shijie@os.amperecomputing.com>,
Kazuhito Hagio <k-hagio-ab@nec.com>,
Lianbo Jiang <lijiang@redhat.com>
Cc: catalin.marinas@arm.com, will@kernel.org, vgoyal@redhat.com,
dyoung@redhat.com, corbet@lwn.net, kexec@lists.infradead.org,
linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, zwang@amperecomputing.com,
patches@amperecomputing.com, darren@os.amperecomputing.com
Subject: Re: [PATCH] arm64: crash_core: Export MODULES, VMALLOC, and VMEMMAP ranges
Date: Wed, 9 Feb 2022 11:16:48 +0800 [thread overview]
Message-ID: <YgMyIOZ+USwLKCQI@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220209092642.9181-1-shijie@os.amperecomputing.com>
On 02/09/22 at 09:26am, Huang Shijie wrote:
> The following interrelated ranges are needed by the kdump crash tool:
> MODULES_VADDR ~ MODULES_END,
> VMALLOC_START ~ VMALLOC_END,
> VMEMMAP_START ~ VMEMMAP_END
>
> Since these values change from time to time, it is preferable to export
> them via vmcoreinfo than to change the crash's code frequently.
Add Kazu and Lianbo to CC since they take care of Crash utility now,
please check if this is necessary for Crash.
>
> Signed-off-by: Huang Shijie <shijie@os.amperecomputing.com>
> ---
> Documentation/admin-guide/kdump/vmcoreinfo.rst | 8 ++++++++
> arch/arm64/kernel/crash_core.c | 6 ++++++
> 2 files changed, 14 insertions(+)
>
> diff --git a/Documentation/admin-guide/kdump/vmcoreinfo.rst b/Documentation/admin-guide/kdump/vmcoreinfo.rst
> index 3861a25faae1..a339af45a22e 100644
> --- a/Documentation/admin-guide/kdump/vmcoreinfo.rst
> +++ b/Documentation/admin-guide/kdump/vmcoreinfo.rst
> @@ -494,6 +494,14 @@ architecture which is used to lookup the page-tables for the Virtual
> addresses in the higher VA range (refer to ARMv8 ARM document for
> more details).
>
> +MODULES_VADDR|MODULES_END|VMALLOC_START|VMALLOC_END|VMEMMAP_START|VMEMMAP_END
> +-------------
> +
> +Used to get the correct ranges:
> + MODULES_VADDR ~ MODULES_END-1 : Kernel module space.
> + VMALLOC_START ~ VMALLOC_END-1 : vmalloc() / ioremap() space.
> + VMEMMAP_START ~ VMEMMAP_END-1 : vmemmap region, used for struct page array.
> +
> arm
> ===
>
> diff --git a/arch/arm64/kernel/crash_core.c b/arch/arm64/kernel/crash_core.c
> index 314391a156ee..2b65aae332ce 100644
> --- a/arch/arm64/kernel/crash_core.c
> +++ b/arch/arm64/kernel/crash_core.c
> @@ -20,6 +20,12 @@ void arch_crash_save_vmcoreinfo(void)
> {
> VMCOREINFO_NUMBER(VA_BITS);
> /* Please note VMCOREINFO_NUMBER() uses "%d", not "%x" */
> + vmcoreinfo_append_str("NUMBER(MODULES_VADDR)=0x%lx\n", MODULES_VADDR);
> + vmcoreinfo_append_str("NUMBER(MODULES_END)=0x%lx\n", MODULES_END);
> + vmcoreinfo_append_str("NUMBER(VMALLOC_START)=0x%lx\n", VMALLOC_START);
> + vmcoreinfo_append_str("NUMBER(VMALLOC_END)=0x%lx\n", VMALLOC_END);
> + vmcoreinfo_append_str("NUMBER(VMEMMAP_START)=0x%lx\n", VMEMMAP_START);
> + vmcoreinfo_append_str("NUMBER(VMEMMAP_END)=0x%lx\n", VMEMMAP_END);
> vmcoreinfo_append_str("NUMBER(kimage_voffset)=0x%llx\n",
> kimage_voffset);
> vmcoreinfo_append_str("NUMBER(PHYS_OFFSET)=0x%llx\n",
> --
> 2.30.2
>
next prev parent reply other threads:[~2022-02-09 3:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 9:26 [PATCH] arm64: crash_core: Export MODULES, VMALLOC, and VMEMMAP ranges Huang Shijie
2022-02-09 3:16 ` Baoquan He [this message]
2022-02-15 16:44 ` Will Deacon
2022-02-16 9:28 ` Huang Shijie
2022-02-16 12:40 ` Will Deacon
2022-02-17 10:01 ` Huang Shijie
2022-02-17 10:29 ` Huang Shijie
2022-03-07 22:03 ` Will Deacon
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=YgMyIOZ+USwLKCQI@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=darren@os.amperecomputing.com \
--cc=dyoung@redhat.com \
--cc=k-hagio-ab@nec.com \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@amperecomputing.com \
--cc=shijie@os.amperecomputing.com \
--cc=vgoyal@redhat.com \
--cc=will@kernel.org \
--cc=zwang@amperecomputing.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).