From: Youling Tang <youling.tang@linux.dev>
To: Simon Horman <horms@verge.net.au>
Cc: Simon Horman <horms@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
kexec@lists.infradead.org, youling.tang@linux.dev,
Youling Tang <tangyouling@kylinos.cn>
Subject: [PATCH v2 00/10] Fix and improve the LoongArch implementation
Date: Tue, 16 Sep 2025 09:46:45 +0800 [thread overview]
Message-ID: <20250916014655.841632-1-youling.tang@linux.dev> (raw)
From: Youling Tang <tangyouling@kylinos.cn>
- Add kexec_file support for LoongArch.
- Fix and improve the LoongArch implementation.
- Fixed the handling of crashkernel parameters when using --reuse-cmdline.
Kernel support for kexec_file was introduced by the patch detailed in Link [1].
Link[1]:
https://lore.kernel.org/loongarch/20250903030100.196744-1-youling.tang@linux.dev/T/#t
Changelog:
v2:
- Add kexec_file support for LoongArch.
- Correct email address and Signed-off-by.
Youling Tang (10):
kexec: Handle removal of multiple 'crashkernel' parameters
LoongArch: Fix comments
LoongArch: Terminate the cmdline string using '\0'
LoongArch: Enforce relocatable kernel check for crash dump
LoongArch: Change initrd allocation to top-down
LoongArch: Fix the use of loongarch_image_header in ELF format
LoongArch: Add pe_hdr->machine check for pei format images
LoongArch/pez: Fix kernel_fd handling when kexec_file is supported
LoongArch: Add kexec_file_load syscall
LoongArch: Remove 'kexec_file' cmdline parameters when using
--reuse-cmdline option
kexec/arch/loongarch/image-header.h | 5 ++-
kexec/arch/loongarch/kexec-elf-loongarch.c | 47 ++++++++++++++++++----
kexec/arch/loongarch/kexec-loongarch.c | 44 +++++++++++++++++++-
kexec/arch/loongarch/kexec-loongarch.h | 1 +
kexec/arch/loongarch/kexec-pei-loongarch.c | 27 ++++++++++++-
kexec/arch/loongarch/kexec-pez-loongarch.c | 14 ++++---
kexec/kexec-syscall.h | 5 ++-
kexec/kexec.c | 6 +++
8 files changed, 130 insertions(+), 19 deletions(-)
--
2.34.1
next reply other threads:[~2025-09-16 1:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 1:46 Youling Tang [this message]
2025-09-16 1:46 ` [PATCH v2 01/10] kexec: Handle removal of multiple 'crashkernel' parameters Youling Tang
2025-09-16 1:46 ` [PATCH v2 02/10] LoongArch: Fix comments Youling Tang
2025-09-16 1:46 ` [PATCH v2 03/10] LoongArch: Terminate the cmdline string using '\0' Youling Tang
2025-09-16 1:46 ` [PATCH v2 04/10] LoongArch: Enforce relocatable kernel check for crash dump Youling Tang
2025-09-16 1:46 ` [PATCH v2 05/10] LoongArch: Change initrd allocation to top-down Youling Tang
2025-09-16 1:46 ` [PATCH v2 06/10] LoongArch: Fix the use of loongarch_image_header in ELF format Youling Tang
2025-09-16 1:46 ` [PATCH v2 07/10] LoongArch: Add pe_hdr->machine check for pei format images Youling Tang
2025-09-16 1:46 ` [PATCH v2 08/10] LoongArch/pez: Fix kernel_fd handling when kexec_file is supported Youling Tang
2025-09-16 1:46 ` [PATCH v2 09/10] LoongArch: Add kexec_file_load syscall Youling Tang
2025-09-16 1:46 ` [PATCH v2 10/10] LoongArch: Remove 'kexec_file' cmdline parameters when using --reuse-cmdline option Youling Tang
2025-09-23 16:51 ` [PATCH v2 00/10] Fix and improve the LoongArch implementation 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=20250916014655.841632-1-youling.tang@linux.dev \
--to=youling.tang@linux.dev \
--cc=chenhuacai@kernel.org \
--cc=horms@kernel.org \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=tangyouling@kylinos.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.