From: Borislav Petkov <bp@alien8.de>
To: Eric DeVolder <eric.devolder@oracle.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
kexec@lists.infradead.org, ebiederm@xmission.com,
dyoung@redhat.com, bhe@redhat.com, vgoyal@redhat.com,
tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, hpa@zytor.com,
nramas@linux.microsoft.com, thomas.lendacky@amd.com,
robh@kernel.org, efault@gmx.de, rppt@kernel.org,
david@redhat.com, sourabhjain@linux.ibm.com,
konrad.wilk@oracle.com, boris.ostrovsky@oracle.com
Subject: Re: [PATCH v14 7/7] x86/crash: add x86 crash hotplug support
Date: Wed, 7 Dec 2022 11:19:58 +0100 [thread overview]
Message-ID: <Y5BozkPot12L5d9w@zn.tnic> (raw)
In-Reply-To: <20221116214643.6384-8-eric.devolder@oracle.com>
On Wed, Nov 16, 2022 at 04:46:43PM -0500, Eric DeVolder wrote:
> When CPU or memory is hot un/plugged, the crash elfcorehdr, which
> describes the CPUs and memory in the system, must also be updated.
>
> A new elfcorehdr is generated from the available CPUs and memory
> into a buffer, and then installed over the top of the existing
> elfcorehdr. The segment containing the elfcorehdr is identified
> at run time in crash_core:handle_hotplug_event(), which works for
> both the kexec_load() and kexec_file_load() syscalls.
>
> In the patch 'kexec: exclude elfcorehdr from the segment digest'
> the need to update purgatory due to the change in elfcorehdr was
> eliminated. As a result, no changes to purgatory or boot_params
> (as the elfcorehdr= kernel command line parameter pointer
> remains unchanged and correct) are needed, just elfcorehdr.
>
> To accommodate a growing number of resources via hotplug, the
> elfcorehdr segment must be sufficiently large enough to accommodate
> changes, see the CRASH_MAX_MEMORY_RANGES description.
>
> Signed-off-by: Eric DeVolder <eric.devolder@oracle.com>
> ---
> arch/x86/Kconfig | 9 +++
> arch/x86/include/asm/kexec.h | 15 +++++
> arch/x86/kernel/crash.c | 106 ++++++++++++++++++++++++++++++++++-
> 3 files changed, 127 insertions(+), 3 deletions(-)
Some quick cleanups ontop, there's potential for more:
---
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index ffee99046942..486509030d3a 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -2091,13 +2091,16 @@ config CRASH_DUMP
For more details see Documentation/admin-guide/kdump/kdump.rst
config CRASH_HOTPLUG
- bool "kernel updates of crash elfcorehdr"
+ bool "Update the crash elfcorehdr on system configuration changes"
default n
depends on CRASH_DUMP && (HOTPLUG_CPU || MEMORY_HOTPLUG)
help
- Enable the kernel to directly update the crash elfcorehdr (which
- contains the list of CPUs and memory regions to be dumped upon
- a crash) in response to hot plug/unplug of CPUs or memory.
+ Enable direct updates to the crash elfcorehdr (which contains
+ the list of CPUs and memory regions to be dumped upon a crash)
+ in response to hot plug/unplug of CPUs or memory. This is a much
+ more advanced approach than userspace attempting that.
+
+ If unsure, say Y.
config KEXEC_JUMP
bool "kexec jump"
diff --git a/arch/x86/kernel/crash.c b/arch/x86/kernel/crash.c
index d2238bcf8106..d26f208e582e 100644
--- a/arch/x86/kernel/crash.c
+++ b/arch/x86/kernel/crash.c
@@ -413,25 +413,32 @@ int crash_load_segments(struct kimage *image)
image->elf_headers_sz = kbuf.bufsz;
kbuf.memsz = kbuf.bufsz;
-#ifdef CONFIG_CRASH_HOTPLUG
- /* Ensure elfcorehdr segment large enough for hotplug changes */
- unsigned long pnum = 2; /* VMCOREINFO and kernel_map */
-
- if (IS_ENABLED(CONFIG_HOTPLUG_CPU))
- pnum += CONFIG_NR_CPUS_DEFAULT;
- if (IS_ENABLED(CONFIG_MEMORY_HOTPLUG))
- pnum += CRASH_MAX_MEMORY_RANGES;
- if (pnum < (unsigned long)PN_XNUM) {
- kbuf.memsz = pnum * sizeof(Elf64_Phdr);
- kbuf.memsz += sizeof(Elf64_Ehdr);
- image->elfcorehdr_index = image->nr_segments;
- image->elfcorehdr_index_valid = true;
- /* Mark as usable to crash kernel, else crash kernel fails on boot */
- image->elf_headers_sz = kbuf.memsz;
- } else {
- pr_err("number of Phdrs %lu exceeds max\n", pnum);
+ if (IS_ENABLED(CONFIG_CRASH_HOTPLUG)) {
+ /*
+ * Ensure the elfcorehdr segment large enough for hotplug changes.
+ * Start with VMCOREINFO and kernel_map:
+ */
+ unsigned long pnum = 2;
+
+ if (IS_ENABLED(CONFIG_HOTPLUG_CPU))
+ pnum += CONFIG_NR_CPUS_DEFAULT;
+
+ if (IS_ENABLED(CONFIG_MEMORY_HOTPLUG))
+ pnum += CRASH_MAX_MEMORY_RANGES;
+
+ if (pnum < (unsigned long)PN_XNUM) {
+ kbuf.memsz = pnum * sizeof(Elf64_Phdr);
+ kbuf.memsz += sizeof(Elf64_Ehdr);
+
+ image->elfcorehdr_index = image->nr_segments;
+ image->elfcorehdr_index_valid = true;
+
+ /* Mark as usable to crash kernel, else crash kernel fails on boot */
+ image->elf_headers_sz = kbuf.memsz;
+ } else {
+ pr_err("number of Phdrs %lu exceeds max\n", pnum);
+ }
}
-#endif
kbuf.buf_align = ELF_CORE_HEADER_ALIGN;
kbuf.mem = KEXEC_BUF_MEM_UNKNOWN;
@@ -463,10 +470,9 @@ int crash_load_segments(struct kimage *image)
*/
void arch_crash_handle_hotplug_event(struct kimage *image)
{
+ void *elfbuf, *old_elfcorehdr;
unsigned long mem, memsz;
- unsigned long elfsz = 0;
- void *elfbuf = NULL;
- void *ptr;
+ unsigned long elfsz;
/*
* Create the new elfcorehdr reflecting the changes to CPU and/or
@@ -489,26 +495,24 @@ void arch_crash_handle_hotplug_event(struct kimage *image)
goto out;
}
- /*
- * Copy new elfcorehdr over the old elfcorehdr at destination.
- */
- ptr = arch_map_crash_pages(mem, memsz);
- if (ptr) {
- /*
- * Temporarily invalidate the crash image while the
- * elfcorehdr is updated.
- */
- xchg(&kexec_crash_image, NULL);
- memcpy_flushcache(ptr, elfbuf, elfsz);
- xchg(&kexec_crash_image, image);
- arch_unmap_crash_pages(ptr);
- pr_debug("updated elfcorehdr\n");
- } else {
+ /* Copy new elfcorehdr over the old elfcorehdr at destination. */
+ old_elfcorehdr = arch_map_crash_pages(mem, memsz);
+ if (!old_elfcorehdr) {
pr_err("updating elfcorehdr failed\n");
+ goto out;
}
+ /*
+ * Temporarily invalidate the crash image while the elfcorehdr
+ * is updated.
+ * */
+ xchg(&kexec_crash_image, NULL);
+ memcpy_flushcache(old_elfcorehdr, elfbuf, elfsz);
+ xchg(&kexec_crash_image, image);
+ arch_unmap_crash_pages(old_elfcorehdr);
+ pr_debug("updated elfcorehdr\n");
+
out:
- if (elfbuf)
- vfree(elfbuf);
+ vfree(elfbuf);
}
#endif
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-12-07 10:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 21:46 [PATCH v14 0/7] crash: Kernel handling of CPU and memory hot un/plug Eric DeVolder
2022-11-16 21:46 ` [PATCH v14 1/7] crash: move crash_prepare_elf64_headers() Eric DeVolder
2022-11-16 21:46 ` [PATCH v14 2/7] crash: prototype change for crash_prepare_elf64_headers() Eric DeVolder
2022-11-16 21:46 ` [PATCH v14 3/7] crash: add generic infrastructure for crash hotplug support Eric DeVolder
2022-11-25 3:26 ` Baoquan He
2022-11-28 15:46 ` Eric DeVolder
2022-11-29 0:43 ` Baoquan He
2022-12-07 10:00 ` Borislav Petkov
2022-12-07 12:36 ` Baoquan He
2022-12-07 12:42 ` Borislav Petkov
2022-12-07 13:57 ` Baoquan He
2022-12-07 15:56 ` Borislav Petkov
2022-12-08 4:03 ` Baoquan He
2022-12-07 10:15 ` Borislav Petkov
2022-12-08 19:04 ` Eric DeVolder
2022-11-16 21:46 ` [PATCH v14 4/7] kexec: exclude elfcorehdr from the segment digest Eric DeVolder
2022-11-16 21:46 ` [PATCH v14 5/7] kexec: exclude hot remove cpu from elfcorehdr notes Eric DeVolder
2022-11-16 21:46 ` [PATCH v14 6/7] crash: memory and cpu hotplug sysfs attributes Eric DeVolder
2022-11-16 21:46 ` [PATCH v14 7/7] x86/crash: add x86 crash hotplug support Eric DeVolder
2022-12-07 10:19 ` Borislav Petkov [this message]
2022-12-08 20:34 ` Eric DeVolder
2022-11-23 15:31 ` [PATCH v14 0/7] crash: Kernel handling of CPU and memory hot un/plug Sourabh Jain
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=Y5BozkPot12L5d9w@zn.tnic \
--to=bp@alien8.de \
--cc=bhe@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=efault@gmx.de \
--cc=eric.devolder@oracle.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nramas@linux.microsoft.com \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=sourabhjain@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=vgoyal@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