From: Dave Young <dyoung@redhat.com>
To: Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: [PATCH] x86/e820: update code comment about e820_table_kexec
Date: Sat, 14 Sep 2024 19:20:52 +0800 [thread overview]
Message-ID: <ZuVxlJ77V2_U0HPM@darkstar.users.ipa.redhat.com> (raw)
The setup_data ranges are not reserved for kexec any more after
commit fc7f27cda843 ("x86/kexec: Do not update E820 kexec table
for setup_data"), so update the code comment here.
Signed-off-by: Dave Young <dyoung@redhat.com>
---
arch/x86/kernel/e820.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
Index: linux-x86/arch/x86/kernel/e820.c
===================================================================
--- linux-x86.orig/arch/x86/kernel/e820.c 2024-09-14 10:39:57.423551301 +0800
+++ linux-x86/arch/x86/kernel/e820.c 2024-09-14 18:56:30.158316496 +0800
@@ -36,10 +36,8 @@
*
* - 'e820_table_kexec': a slightly modified (by the kernel) firmware version
* passed to us by the bootloader - the major difference between
- * e820_table_firmware[] and this one is that, the latter marks the setup_data
- * list created by the EFI boot stub as reserved, so that kexec can reuse the
- * setup_data information in the second kernel. Besides, e820_table_kexec[]
- * might also be modified by the kexec itself to fake a mptable.
+ * e820_table_firmware[] and this one is that e820_table_kexec[]
+ * might be modified by the kexec itself to fake a mptable.
* We use this to:
*
* - kexec, which is a bootloader in disguise, uses the original E820
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2024-09-14 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 11:20 Dave Young [this message]
2024-09-14 11:35 ` [PATCH] x86/e820: update code comment about e820_table_kexec Dave Young
2025-01-10 6:29 ` Dave Young
2025-01-10 6:34 ` Dave Young
2025-01-14 3:26 ` Chen, Yu C
2025-01-14 3:57 ` Dave Young
2025-01-28 13:48 ` Dave Young
2024-09-30 3:00 ` Baoquan He
2025-01-10 6:21 ` Dave Young
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=ZuVxlJ77V2_U0HPM@darkstar.users.ipa.redhat.com \
--to=dyoung@redhat.com \
--cc=bp@alien8.de \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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