From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Xianting Tian <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, heinrich.schuchardt@canonical.com,
k-hagio-ab@nec.com, hschauhan@nulltrace.org, yixun.lan@gmail.com
Subject: Re: [PATCH V6 6/6] Documentation: kdump: describe VMCOREINFO export for RISCV64
Date: Thu, 11 Aug 2022 20:27:05 +0700 [thread overview]
Message-ID: <f2336f93-53b4-b031-9e1c-67b6d1470f64@gmail.com> (raw)
In-Reply-To: <20220811074150.3020189-7-xianting.tian@linux.alibaba.com>
On 8/11/22 14:41, Xianting Tian wrote:
> The following interrelated definitions and ranges are needed by the kdump
> crash tool, they are exported by "arch/riscv/kernel/crash_core.c":
> VA_BITS, PAGE_OFFSET, phys_ram_base
> MODULES_VADDR ~ MODULES_END,
> VMALLOC_START ~ VMALLOC_END,
> VMEMMAP_START ~ VMEMMAP_END
> KASAN_SHADOW_START ~ KASAN_SHADOW_END,
> KERNEL_LINK_ADDR ~ ADDRESS_SPACE_END
>
> This patch just add the description of VMCOREINFO export for RISCV64.
>
Better say "Document these RISCV64 exports above".
--
An old man doll... just what I always wanted! - Clara
_______________________________________________
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-11 13:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 7:41 [PATCH V6 0/6] RISC-V fixups to work with crash tool Xianting Tian
2022-08-11 7:41 ` [PATCH V6 1/6] RISC-V: kexec: Fixup use of smp_processor_id() in preemptible context Xianting Tian
2022-08-11 7:41 ` [PATCH V6 2/6] RISC-V: Fixup get incorrect user mode PC for kernel mode regs Xianting Tian
2022-08-11 7:41 ` [PATCH V6 3/6] RISC-V: Fixup schedule out issue in machine_crash_shutdown() Xianting Tian
2022-08-11 7:41 ` [PATCH V6 4/6] RISC-V: Add modules to virtual kernel memory layout dump Xianting Tian
2022-08-11 7:41 ` [PATCH V6 5/6] RISC-V: Add arch_crash_save_vmcoreinfo support Xianting Tian
2022-08-11 7:41 ` [PATCH V6 6/6] Documentation: kdump: describe VMCOREINFO export for RISCV64 Xianting Tian
2022-08-11 13:27 ` Bagas Sanjaya [this message]
2022-08-11 15:45 ` [PATCH V6 0/6] RISC-V fixups to work with crash tool Conor.Dooley
2022-08-11 16:17 ` Palmer Dabbelt
2022-08-12 3:23 ` Xianting Tian
2022-09-15 18:57 ` Conor.Dooley
2022-10-12 9:42 ` Xianting Tian
2022-10-12 9:52 ` Conor Dooley
2022-10-13 2:28 ` Xianting Tian
2022-10-13 5:24 ` Conor Dooley
2022-10-13 9:26 ` Xianting Tian
2022-10-14 7:53 ` 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=f2336f93-53b4-b031-9e1c-67b6d1470f64@gmail.com \
--to=bagasdotme@gmail.com \
--cc=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=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 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).