From: Simon Horman <horms@kernel.org>
To: WANG Rui <wangrui@loongson.cn>
Cc: kexec@lists.infradead.org, Huacai Chen <chenhuacai@kernel.org>
Subject: Re: [PATCH] LoongArch: Load vmlinux.efi to the link address
Date: Mon, 27 Nov 2023 13:46:53 +0000 [thread overview]
Message-ID: <20231127134653.GC3354982@kernel.org> (raw)
In-Reply-To: <20231124154658.114579-1-wangrui@loongson.cn>
On Fri, Nov 24, 2023 at 11:46:58PM +0800, WANG Rui wrote:
> Currently, kexec loads vmlinux.efi to address 0 instead of the link
> address. This causes kexec to fail to boot the new vmlinux.efi on qemu.
>
> pei_loongarch_load: kernel_segment: 0000000000000000
> pei_loongarch_load: kernel_entry: 00000000015dc000
> pei_loongarch_load: image_size: 0000000001f30000
> pei_loongarch_load: text_offset: 0000000000200000
> pei_loongarch_load: phys_offset: 0000000000000000
> pei_loongarch_load: PE format: yes
> loongarch_load_other_segments:333: command_line: kexec console=ttyS0,115200
> kexec_load: entry = 0x15dc000 flags = 0x1020000
> nr_segments = 2
> segment[0].buf = 0x7fffef664010
> segment[0].bufsz = 0x1de9a00
> segment[0].mem = (nil)
> segment[0].memsz = 0x1f30000
> segment[1].buf = 0x555555e480b0
> segment[1].bufsz = 0x200
> segment[1].mem = 0x1f30000
> segment[1].memsz = 0x4000
>
> This patch adds `text_offset` when adding kernel segment to load
> vmlinux.efi to the link address.
>
> pei_loongarch_load: kernel_segment: 0000000000000000
> pei_loongarch_load: kernel_entry: 00000000015dc000
> pei_loongarch_load: image_size: 0000000001f30000
> pei_loongarch_load: text_offset: 0000000000200000
> pei_loongarch_load: phys_offset: 0000000000000000
> pei_loongarch_load: PE format: yes
> loongarch_load_other_segments:335: command_line: kexec console=ttyS0,115200
> kexec_load: entry = 0x15dc000 flags = 0x1020000
> nr_segments = 2
> segment[0].buf = 0x7ffff1a04010
> segment[0].bufsz = 0x1de9a00
> segment[0].mem = 0x200000
> segment[0].memsz = 0x1f30000
> segment[1].buf = 0x555555b28098
> segment[1].bufsz = 0x200
> segment[1].mem = 0x2130000
> segment[1].memsz = 0x4000
>
> Signed-off-by: WANG Rui <wangrui@loongson.cn>
Thanks, applied.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2023-11-27 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 15:46 [PATCH] LoongArch: Load vmlinux.efi to the link address WANG Rui
2023-11-27 13:46 ` Simon Horman [this message]
2023-12-02 10:11 ` WANG Rui
2023-12-02 12:30 ` Huacai Chen
2023-12-02 12:46 ` Simon Horman
2023-12-02 14:03 ` Huacai Chen
2023-12-02 16:35 ` Simon Horman
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=20231127134653.GC3354982@kernel.org \
--to=horms@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=wangrui@loongson.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox