From: Simon Horman <horms@kernel.org>
To: luo.haiyang@zte.com.cn
Cc: kexec@lists.infradead.org, zhang.run@zte.com.cn, cai.qu@zte.com.cn
Subject: Re: [PATCH v4 2/4] RISCV: Fix incorrect virtual address translation in? crashdump load
Date: Wed, 27 May 2026 08:27:09 +0100 [thread overview]
Message-ID: <20260527072709.GA51310@horms.kernel.org> (raw)
In-Reply-To: <20260521120946097C8qpZkVC2mBT_ozYEHlhp@zte.com.cn>
On Thu, May 21, 2026 at 12:09:46PM +0800, luo.haiyang@zte.com.cn wrote:
> From: Luo Haiyang <luo.haiyang@zte.com.cn>
>
> The kexec shows the following crashdump log:
>
> Elf header: p_type = 1, p_offset = 0x80100000 p_paddr = 0x80100000 p_vaddr = 0xcff000 ...
> Elf header: p_type = 1, p_offset = 0x100000000 p_paddr = 0x100000000 p_vaddr = 0x80bff000 ...
> Elf header: p_type = 1, p_offset = 0x87ffff000 p_paddr = 0x87ffff000 p_vaddr = 0x800bfe000 ...
>
> Obviously, phys_to_virt returns an incorrect virtual address (vaddr). On the RISC-V architecture,
> the linear address mapping is defined as:
> va = pa + kernel_map.va_pa_offset (kernel_map.va_pa_offset = PAGE_OFFSET - phys_ram_base)
> Both PAGE_OFFSET and phys_ram_base can be read from /proc/kcore.
>
> Signed-off-by: Luo Haiyang <luo.haiyang@zte.com.cn>
Hi,
Unfortunately this patch seems to be somewhat mangled
and does not apply. Could you look into that?
next prev parent reply other threads:[~2026-05-27 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 4:06 [PATCH v4 0/4] kexec-tool：bug fix for crashdump load on riscv luo.haiyang
2026-05-21 4:08 ` [PATCH v4 1/4] RISC-V: fix crashdump load memory ranges luo.haiyang
2026-05-21 4:09 ` [PATCH v4 2/4] RISCV: Fix incorrect virtual address translation in crashdump load luo.haiyang
2026-05-27 7:27 ` Simon Horman [this message]
2026-05-27 8:18 ` luo.haiyang
2026-05-27 8:30 ` [PATCH v4 2/4] RISCV: Fix incorrect virtual address translation in? " luo.haiyang
2026-05-21 4:12 ` [PATCH v4 3/4] RISC-V: use kernel image to creat kernel text elf header luo.haiyang
2026-05-21 4:13 ` [PATCH v4 4/4] RISC-V: kernel image memory rang should not be excluded luo.haiyang
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=20260527072709.GA51310@horms.kernel.org \
--to=horms@kernel.org \
--cc=cai.qu@zte.com.cn \
--cc=kexec@lists.infradead.org \
--cc=luo.haiyang@zte.com.cn \
--cc=zhang.run@zte.com.cn \
/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.