All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Yangyang Lian" <lianyangyang@kylinos.cn>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Pratyush Yadav" <pratyush@kernel.org>,
	"Pasha Tatashin" <pasha.tatashin@soleen.com>,
	"Huacai Chen" <chenhuacai@kernel.org>,
	"Mike Rapoport" <rppt@kernel.org>,
	"Baoquan He" <baoquan.he@linux.dev>
Cc: "WANG Xuerui" <kernel@xen0n.name>, "Tao Cui" <cuitao@kylinos.cn>,
	"Dave Young" <ruirui.yang@linux.dev>,
	"George Guo" <guodongtai@kylinos.cn>,
	kexec@lists.infradead.org, loongarch@lists.linux.dev,
	"Haoran Jiang" <jianghaoran@kylinos.cn>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] LoongArch: kdump: add arch_crash_save_vmcoreinfo() support
Date: Thu, 24 Sep 2026 08:04:53 +0000	[thread overview]
Message-ID: <20260924080454.30B681F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260924075655.375632-1-lianyangyang@kylinos.cn>

> Since commit 23c85094fe18 ("proc/kcore: add vmcoreinfo note to
> /proc/kcore") the kernel has exported the vmcoreinfo PT_NOTE on
> /proc/kcore as wellas /proc/vmcore.
> 
> LoongArch does not provide arch_crash_save_vmcoreinfo(), so the
> arch-specific values are missing from the vmcoreinfo PT_NOTE. The
> generic exporter in kernel/vmcore_info.c already provides
> NUMBER(VMALLOC_START), but tools like crash cannot derive the module
> and vmemmap ranges, VA_BITS, or the KASLR offset of a LoongArch dump.
> 
> Since commit 18210a104bb9 ("LoongArch: Expand module virtual address
> space to 2GB") the vmalloc and module boundaries are no longer stable
> across kernel versions either, so vmcoreinfo is the only reliable
> source for them.
> 
> Provide this function in a separate file that is built at the same time
> as its caller in kernel/vmcore_info.c, and add a LOONGARCH64 section to
> Documentation/admin-guide/kdump/vmcoreinfo.rst.
> 
> Reported-by: Haoran Jiang <jianghaoran@kylinos.cn>
> Suggested-by: Haoran Jiang <jianghaoran@kylinos.cn>
> Tested-by: Tao Cui <cuitao@kylinos.cn>
> Co-developed-by: George Guo <guodongtai@kylinos.cn>
> Signed-off-by: George Guo <guodongtai@kylinos.cn>
> Signed-off-by: Yangyang Lian <lianyangyang@kylinos.cn>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260924075655.375632-1-lianyangyang@kylinos.cn?part=1


  reply	other threads:[~2026-09-24  8:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23  6:03 [PATCH] LoongArch: kdump: add arch_crash_save_vmcoreinfo() support Yangyang Lian
2026-09-23  6:16 ` sashiko-bot
2026-09-24  2:23 ` Tao Cui
2026-09-24  7:56 ` [PATCH v2] " Yangyang Lian
2026-09-24  8:04   ` sashiko-bot [this message]
2026-09-28 14:28   ` Huacai Chen
2026-10-03  8:23     ` Dave Young
2026-10-03  9:10       ` Huacai Chen
2026-10-10  5:41         ` Dave Young
2026-10-08  2:34   ` [PATCH v3] " Yangyang Lian
2026-10-08  2:48     ` sashiko-bot
2026-10-11 14:25     ` Huacai Chen

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=20260924080454.30B681F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=baoquan.he@linux.dev \
    --cc=chenhuacai@kernel.org \
    --cc=cuitao@kylinos.cn \
    --cc=guodongtai@kylinos.cn \
    --cc=jianghaoran@kylinos.cn \
    --cc=kernel@xen0n.name \
    --cc=kexec@lists.infradead.org \
    --cc=lianyangyang@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --cc=rppt@kernel.org \
    --cc=ruirui.yang@linux.dev \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.