From: <Conor.Dooley@microchip.com>
To: <xianting.tian@linux.alibaba.com>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<anup@brainfault.org>, <heiko@sntech.de>, <guoren@kernel.org>,
<mick@ics.forth.gr>, <alexandre.ghiti@canonical.com>,
<bhe@redhat.com>, <vgoyal@redhat.com>, <dyoung@redhat.com>,
<corbet@lwn.net>, <Conor.Dooley@microchip.com>
Cc: <kexec@lists.infradead.org>, <linux-doc@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<crash-utility@redhat.com>, <huanyi.xj@alibaba-inc.com>,
<heinrich.schuchardt@canonical.com>, <k-hagio-ab@nec.com>,
<hschauhan@nulltrace.org>, <yixun.lan@gmail.com>
Subject: Re: [PATCH V5 5/6] riscv: crash_core: Export kernel vm layout, phys_ram_base
Date: Tue, 9 Aug 2022 21:20:01 +0000 [thread overview]
Message-ID: <cf03285d-62e7-c70a-4197-8519fe9effe0@microchip.com> (raw)
In-Reply-To: <20220802121818.2201268-6-xianting.tian@linux.alibaba.com>
On 02/08/2022 13:18, Xianting Tian wrote:
> riscv: crash_core: Export kernel vm layout, phys_ram_base
Can you please just use RISC-V: for the whole series, my OCD
hates the mix haha.
> These infos are needed by the kdump crash tool. Since these values change
> from time to time, it is preferable to export them via vmcoreinfo than to
> change the crash's code frequently.
This commit description doesn't seem to match the patches at all.
I don't see any exporting happening here at all - this is documenting
the export. Maybe I am just misunderstanding, but this commit message
just doesn't seem to match the change. Secondly, should the subject not
be something like "docs: admin-guide: add riscv crash kernel yada yada"?
Maybe the current subject lime that explains the lack of a review from
the docs maintainer?
Thanks,
Conor.
>
> Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
> ---
> .../admin-guide/kdump/vmcoreinfo.rst | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/Documentation/admin-guide/kdump/vmcoreinfo.rst b/Documentation/admin-guide/kdump/vmcoreinfo.rst
> index 8419019b6a88..6b76284a503c 100644
> --- a/Documentation/admin-guide/kdump/vmcoreinfo.rst
> +++ b/Documentation/admin-guide/kdump/vmcoreinfo.rst
> @@ -595,3 +595,34 @@ X2TLB
> -----
>
> Indicates whether the crashed kernel enabled SH extended mode.
> +
> +RISCV64
> +=======
> +
> +VA_BITS
> +-------
> +
> +The maximum number of bits for virtual addresses. Used to compute the
> +virtual memory ranges.
> +
> +PAGE_OFFSET
> +-----------
> +
> +Indicates the virtual kernel start address of direct-mapped RAM region.
> +
> +phys_ram_base
> +-------------
> +
> +Indicates the start physical RAM address.
> +
> +MODULES_VADDR|MODULES_END|VMALLOC_START|VMALLOC_END|VMEMMAP_START|VMEMMAP_END
> +-----------------------------------------------------------------------------
> +KASAN_SHADOW_START|KASAN_SHADOW_END|KERNEL_LINK_ADDR|ADDRESS_SPACE_END
> +----------------------------------------------------------------------
> +
> +Used to get the correct ranges:
> + MODULES_VADDR ~ MODULES_END : Kernel module space.
> + VMALLOC_START ~ VMALLOC_END : vmalloc() / ioremap() space.
> + VMEMMAP_START ~ VMEMMAP_END : vmemmap region, used for struct page array.
> + KASAN_SHADOW_START ~ KASAN_SHADOW_END : kasan shadow space.
> + KERNEL_LINK_ADDR ~ ADDRESS_SPACE_END : Kernel link and BPF space.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <xianting.tian@linux.alibaba.com>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<anup@brainfault.org>, <heiko@sntech.de>, <guoren@kernel.org>,
<mick@ics.forth.gr>, <alexandre.ghiti@canonical.com>,
<bhe@redhat.com>, <vgoyal@redhat.com>, <dyoung@redhat.com>,
<corbet@lwn.net>, <Conor.Dooley@microchip.com>
Cc: <kexec@lists.infradead.org>, <linux-doc@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<crash-utility@redhat.com>, <huanyi.xj@alibaba-inc.com>,
<heinrich.schuchardt@canonical.com>, <k-hagio-ab@nec.com>,
<hschauhan@nulltrace.org>, <yixun.lan@gmail.com>
Subject: Re: [PATCH V5 5/6] riscv: crash_core: Export kernel vm layout, phys_ram_base
Date: Tue, 9 Aug 2022 21:20:01 +0000 [thread overview]
Message-ID: <cf03285d-62e7-c70a-4197-8519fe9effe0@microchip.com> (raw)
In-Reply-To: <20220802121818.2201268-6-xianting.tian@linux.alibaba.com>
On 02/08/2022 13:18, Xianting Tian wrote:
> riscv: crash_core: Export kernel vm layout, phys_ram_base
Can you please just use RISC-V: for the whole series, my OCD
hates the mix haha.
> These infos are needed by the kdump crash tool. Since these values change
> from time to time, it is preferable to export them via vmcoreinfo than to
> change the crash's code frequently.
This commit description doesn't seem to match the patches at all.
I don't see any exporting happening here at all - this is documenting
the export. Maybe I am just misunderstanding, but this commit message
just doesn't seem to match the change. Secondly, should the subject not
be something like "docs: admin-guide: add riscv crash kernel yada yada"?
Maybe the current subject lime that explains the lack of a review from
the docs maintainer?
Thanks,
Conor.
>
> Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
> ---
> .../admin-guide/kdump/vmcoreinfo.rst | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/Documentation/admin-guide/kdump/vmcoreinfo.rst b/Documentation/admin-guide/kdump/vmcoreinfo.rst
> index 8419019b6a88..6b76284a503c 100644
> --- a/Documentation/admin-guide/kdump/vmcoreinfo.rst
> +++ b/Documentation/admin-guide/kdump/vmcoreinfo.rst
> @@ -595,3 +595,34 @@ X2TLB
> -----
>
> Indicates whether the crashed kernel enabled SH extended mode.
> +
> +RISCV64
> +=======
> +
> +VA_BITS
> +-------
> +
> +The maximum number of bits for virtual addresses. Used to compute the
> +virtual memory ranges.
> +
> +PAGE_OFFSET
> +-----------
> +
> +Indicates the virtual kernel start address of direct-mapped RAM region.
> +
> +phys_ram_base
> +-------------
> +
> +Indicates the start physical RAM address.
> +
> +MODULES_VADDR|MODULES_END|VMALLOC_START|VMALLOC_END|VMEMMAP_START|VMEMMAP_END
> +-----------------------------------------------------------------------------
> +KASAN_SHADOW_START|KASAN_SHADOW_END|KERNEL_LINK_ADDR|ADDRESS_SPACE_END
> +----------------------------------------------------------------------
> +
> +Used to get the correct ranges:
> + MODULES_VADDR ~ MODULES_END : Kernel module space.
> + VMALLOC_START ~ VMALLOC_END : vmalloc() / ioremap() space.
> + VMEMMAP_START ~ VMEMMAP_END : vmemmap region, used for struct page array.
> + KASAN_SHADOW_START ~ KASAN_SHADOW_END : kasan shadow space.
> + KERNEL_LINK_ADDR ~ ADDRESS_SPACE_END : Kernel link and BPF space.
WARNING: multiple messages have this Message-ID (diff)
From: <Conor.Dooley@microchip.com>
To: <xianting.tian@linux.alibaba.com>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<anup@brainfault.org>, <heiko@sntech.de>, <guoren@kernel.org>,
<mick@ics.forth.gr>, <alexandre.ghiti@canonical.com>,
<bhe@redhat.com>, <vgoyal@redhat.com>, <dyoung@redhat.com>,
<corbet@lwn.net>, <Conor.Dooley@microchip.com>
Cc: <kexec@lists.infradead.org>, <linux-doc@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<crash-utility@redhat.com>, <huanyi.xj@alibaba-inc.com>,
<heinrich.schuchardt@canonical.com>, <k-hagio-ab@nec.com>,
<hschauhan@nulltrace.org>, <yixun.lan@gmail.com>
Subject: Re: [PATCH V5 5/6] riscv: crash_core: Export kernel vm layout, phys_ram_base
Date: Tue, 9 Aug 2022 21:20:01 +0000 [thread overview]
Message-ID: <cf03285d-62e7-c70a-4197-8519fe9effe0@microchip.com> (raw)
In-Reply-To: <20220802121818.2201268-6-xianting.tian@linux.alibaba.com>
On 02/08/2022 13:18, Xianting Tian wrote:
> riscv: crash_core: Export kernel vm layout, phys_ram_base
Can you please just use RISC-V: for the whole series, my OCD
hates the mix haha.
> These infos are needed by the kdump crash tool. Since these values change
> from time to time, it is preferable to export them via vmcoreinfo than to
> change the crash's code frequently.
This commit description doesn't seem to match the patches at all.
I don't see any exporting happening here at all - this is documenting
the export. Maybe I am just misunderstanding, but this commit message
just doesn't seem to match the change. Secondly, should the subject not
be something like "docs: admin-guide: add riscv crash kernel yada yada"?
Maybe the current subject lime that explains the lack of a review from
the docs maintainer?
Thanks,
Conor.
>
> Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
> ---
> .../admin-guide/kdump/vmcoreinfo.rst | 31 +++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/Documentation/admin-guide/kdump/vmcoreinfo.rst b/Documentation/admin-guide/kdump/vmcoreinfo.rst
> index 8419019b6a88..6b76284a503c 100644
> --- a/Documentation/admin-guide/kdump/vmcoreinfo.rst
> +++ b/Documentation/admin-guide/kdump/vmcoreinfo.rst
> @@ -595,3 +595,34 @@ X2TLB
> -----
>
> Indicates whether the crashed kernel enabled SH extended mode.
> +
> +RISCV64
> +=======
> +
> +VA_BITS
> +-------
> +
> +The maximum number of bits for virtual addresses. Used to compute the
> +virtual memory ranges.
> +
> +PAGE_OFFSET
> +-----------
> +
> +Indicates the virtual kernel start address of direct-mapped RAM region.
> +
> +phys_ram_base
> +-------------
> +
> +Indicates the start physical RAM address.
> +
> +MODULES_VADDR|MODULES_END|VMALLOC_START|VMALLOC_END|VMEMMAP_START|VMEMMAP_END
> +-----------------------------------------------------------------------------
> +KASAN_SHADOW_START|KASAN_SHADOW_END|KERNEL_LINK_ADDR|ADDRESS_SPACE_END
> +----------------------------------------------------------------------
> +
> +Used to get the correct ranges:
> + MODULES_VADDR ~ MODULES_END : Kernel module space.
> + VMALLOC_START ~ VMALLOC_END : vmalloc() / ioremap() space.
> + VMEMMAP_START ~ VMEMMAP_END : vmemmap region, used for struct page array.
> + KASAN_SHADOW_START ~ KASAN_SHADOW_END : kasan shadow space.
> + KERNEL_LINK_ADDR ~ ADDRESS_SPACE_END : Kernel link and BPF space.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-08-09 21:20 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 12:18 [PATCH V5 0/6] RISC-V fixups to work with crash tool Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-02 12:18 ` [PATCH V5 1/6] RISC-V: use __smp_processor_id() instead of smp_processor_id() Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-09 21:10 ` Conor.Dooley
2022-08-09 21:10 ` Conor.Dooley
2022-08-09 21:10 ` Conor.Dooley
2022-08-02 12:18 ` [PATCH V5 2/6] RISC-V: Add arch_crash_save_vmcoreinfo support Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-02 12:18 ` [PATCH V5 3/6] riscv: Add modules to virtual kernel memory layout dump Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-02 12:18 ` [PATCH V5 4/6] RISC-V: Fixup getting correct current pc Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-09 21:13 ` Conor.Dooley
2022-08-09 21:13 ` Conor.Dooley
2022-08-09 21:13 ` Conor.Dooley
2022-08-09 21:14 ` Conor.Dooley
2022-08-09 21:14 ` Conor.Dooley
2022-08-09 21:14 ` Conor.Dooley
2022-08-02 12:18 ` [PATCH V5 5/6] riscv: crash_core: Export kernel vm layout, phys_ram_base Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-09 21:20 ` Conor.Dooley [this message]
2022-08-09 21:20 ` Conor.Dooley
2022-08-09 21:20 ` Conor.Dooley
2022-08-10 12:00 ` Xianting Tian
2022-08-10 12:00 ` Xianting Tian
2022-08-10 12:00 ` Xianting Tian
2022-08-11 3:06 ` Bagas Sanjaya
2022-08-11 3:06 ` Bagas Sanjaya
2022-08-11 3:06 ` Bagas Sanjaya
2022-08-11 3:37 ` Xianting Tian
2022-08-11 3:37 ` Xianting Tian
2022-08-11 3:37 ` Xianting Tian
2022-08-02 12:18 ` [PATCH V5 6/6] RISC-V: Fixup schedule out issue in machine_crash_shutdown() Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-02 12:18 ` Xianting Tian
2022-08-09 21:20 ` Conor.Dooley
2022-08-09 21:20 ` Conor.Dooley
2022-08-09 21:20 ` Conor.Dooley
2022-08-09 6:58 ` [PATCH V5 0/6] RISC-V fixups to work with crash tool Xianting Tian
2022-08-09 6:58 ` Xianting Tian
2022-08-09 6:58 ` Xianting Tian
2022-08-09 21:24 ` Conor.Dooley
2022-08-09 21:24 ` Conor.Dooley
2022-08-09 21:24 ` Conor.Dooley
2022-08-11 2:54 ` Xianting Tian
2022-08-11 2:54 ` Xianting Tian
2022-08-11 2:54 ` Xianting Tian
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=cf03285d-62e7-c70a-4197-8519fe9effe0@microchip.com \
--to=conor.dooley@microchip.com \
--cc=alexandre.ghiti@canonical.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=crash-utility@redhat.com \
--cc=dyoung@redhat.com \
--cc=guoren@kernel.org \
--cc=heiko@sntech.de \
--cc=heinrich.schuchardt@canonical.com \
--cc=hschauhan@nulltrace.org \
--cc=huanyi.xj@alibaba-inc.com \
--cc=k-hagio-ab@nec.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=vgoyal@redhat.com \
--cc=xianting.tian@linux.alibaba.com \
--cc=yixun.lan@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.