All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Austin Kim <austindh.kim@gmail.com>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	 linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	 austin.kim@lge.com
Subject: Re: [PATCH 2/2] riscv: export kaslr offset and satp in VMCOREINFO ELF notes
Date: Thu, 12 Feb 2026 17:45:13 -0700 (MST)	[thread overview]
Message-ID: <ff7ba7eb-dab9-ad4b-1497-83e3530325d6@kernel.org> (raw)
In-Reply-To: <aYwKUE3ZzN7/ZY/A@adminpc-PowerEdge-R7525>

On Wed, 11 Feb 2026, Austin Kim wrote:

> From: Austin Kim <austin.kim@lge.com>
> 
> The following options are required by the kdump crash utility for RISC-V
> based vmcore file:
> 
> - kaslr: If the vmcore is generated from a KASLR-enabled Linux kernel,
>          the KASLR offset is required for the crash utility to load
>          the vmcore. Without the proper kaslr option, the crash utility
>          fails to load the vmcore file.
> - satp: The exact root page table address helps determine the correct base
>         PGD address.
> 
> With this patch, RISC-V VMCOREINFO ELF notes now include both kaslr
> and satp information.
> 
> Signed-off-by: Austin Kim <austin.kim@lge.com>

Thanks, queued for v7.0-rc.


- Paul

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <pjw@kernel.org>
To: Austin Kim <austindh.kim@gmail.com>
Cc: Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	 linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	 austin.kim@lge.com
Subject: Re: [PATCH 2/2] riscv: export kaslr offset and satp in VMCOREINFO ELF notes
Date: Thu, 12 Feb 2026 17:45:13 -0700 (MST)	[thread overview]
Message-ID: <ff7ba7eb-dab9-ad4b-1497-83e3530325d6@kernel.org> (raw)
In-Reply-To: <aYwKUE3ZzN7/ZY/A@adminpc-PowerEdge-R7525>

On Wed, 11 Feb 2026, Austin Kim wrote:

> From: Austin Kim <austin.kim@lge.com>
> 
> The following options are required by the kdump crash utility for RISC-V
> based vmcore file:
> 
> - kaslr: If the vmcore is generated from a KASLR-enabled Linux kernel,
>          the KASLR offset is required for the crash utility to load
>          the vmcore. Without the proper kaslr option, the crash utility
>          fails to load the vmcore file.
> - satp: The exact root page table address helps determine the correct base
>         PGD address.
> 
> With this patch, RISC-V VMCOREINFO ELF notes now include both kaslr
> and satp information.
> 
> Signed-off-by: Austin Kim <austin.kim@lge.com>

Thanks, queued for v7.0-rc.


- Paul

  reply	other threads:[~2026-02-13  0:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  4:49 [PATCH 2/2] riscv: export kaslr offset and satp in VMCOREINFO ELF notes Austin Kim
2026-02-11  4:49 ` Austin Kim
2026-02-13  0:45 ` Paul Walmsley [this message]
2026-02-13  0:45   ` Paul Walmsley

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=ff7ba7eb-dab9-ad4b-1497-83e3530325d6@kernel.org \
    --to=pjw@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=austin.kim@lge.com \
    --cc=austindh.kim@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.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.