From: Brian Mak <makb@juniper.net>
To: Baoquan He <bhe@redhat.com>, Dave Young <dyoung@redhat.com>,
"Alexander Graf" <graf@amazon.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
Rob Herring <robh@kernel.org>,
"Saravana Kannan" <saravanak@google.com>, <x86@kernel.org>,
<kexec@lists.infradead.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Brian Mak <makb@juniper.net>
Subject: [PATCH v2 0/2] x86/kexec: Carry forward the boot DTB on kexec
Date: Tue, 5 Aug 2025 14:15:25 -0700 [thread overview]
Message-ID: <20250805211527.122367-1-makb@juniper.net> (raw)
Hi all,
Here is v2 with the comments from v1 addressed. I also added a patch to
the series to add KEXEC_FILE_NO_CMA as a legal flag. I noticed that this
was missing when I went to add my KEXEC_FILE_FORCE_DTB flag.
Thanks,
Brian
Changes in v2:
- Added a patch to add KEXEC_FILE_NO_CMA as a legal flag
- Added a KEXEC_FILE_FORCE_DTB flag to enable carrying over the current
boot's DTB on x86.
- Modified the commit message to include more reasoning for the change.
- Changed a pr_info print to a pr_debug print.
Brian Mak (2):
kexec: Add KEXEC_FILE_NO_CMA as a legal flag
x86/kexec: Carry forward the boot DTB on kexec
arch/x86/kernel/kexec-bzimage64.c | 47 +++++++++++++++++++++++++++++--
include/linux/kexec.h | 6 +++-
include/uapi/linux/kexec.h | 4 +++
kernel/kexec_file.c | 1 +
4 files changed, 54 insertions(+), 4 deletions(-)
base-commit: 35a813e010b99894bb4706c56c16a580bf7959c2
--
2.25.1
next reply other threads:[~2025-08-05 21:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 21:15 Brian Mak [this message]
2025-08-05 21:15 ` [PATCH v2 1/2] kexec: Add KEXEC_FILE_NO_CMA as a legal flag Brian Mak
2025-08-21 4:47 ` Andrew Morton
2025-08-21 8:33 ` Baoquan He
2025-08-21 11:53 ` Andrew Morton
2025-08-22 3:33 ` Baoquan He
2025-08-25 18:49 ` Brian Mak
2025-09-04 19:58 ` Brian Mak
2025-08-21 16:22 ` Brian Mak
2025-08-05 21:15 ` [PATCH v2 2/2] x86/kexec: Carry forward the boot DTB on kexec Brian Mak
2025-08-12 18:00 ` [PATCH v2 0/2] " Brian Mak
2025-08-13 3:54 ` Dave Young
2025-08-13 19:24 ` Brian Mak
2025-08-14 2:39 ` Baoquan He
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=20250805211527.122367-1-makb@juniper.net \
--to=makb@juniper.net \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dyoung@redhat.com \
--cc=graf@amazon.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).