From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>, linuxppc-dev@ozlabs.org
Cc: David Hildenbrand <david@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Mimi Zohar <zohar@linux.ibm.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Valentin Schneider <vschneid@redhat.com>,
Baoquan He <bhe@redhat.com>,
x86@kernel.org, "Aneesh Kumar K . V" <aneesh.kumar@kernel.org>,
Laurent Dufour <laurent.dufour@fr.ibm.com>,
Dave Young <dyoung@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
Naveen N Rao <naveen@kernel.org>, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
Oscar Salvador <osalvador@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kexec@lists.infradead.org,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Akhil Raj <lf32.dev@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v15 5/5] powerpc: add crash memory hotplug support
Date: Mon, 29 Jan 2024 12:16:01 +0530 [thread overview]
Message-ID: <d2996e30-cd3c-461a-8f8f-46dfb8938407@linux.ibm.com> (raw)
In-Reply-To: <bd82e721-e674-4cfe-b9bf-942aaf7ee52c@linux.ibm.com>
On 23/01/24 15:52, Hari Bathini wrote:
>
>
> On 11/01/24 4:21 pm, Sourabh Jain wrote:
>> Extend the arch crash hotplug handler, as introduced by the patch title
>> ("powerpc: add crash CPU hotplug support"), to also support memory
>> add/remove events.
>>
>> Elfcorehdr describes the memory of the crash kernel to capture the
>> kernel; hence, it needs to be updated if memory resources change due to
>> memory add/remove events. Therefore, arch_crash_handle_hotplug_event()
>> is updated to recreate the elfcorehdr and replace it with the previous
>> one on memory add/remove events.
>>
>> The memblock list is used to prepare the elfcorehdr. In the case of
>> memory hot removal, the memblock list is updated after the arch crash
>> hotplug handler is triggered, as depicted in Figure 1. Thus, the
>> hot-removed memory is explicitly removed from the crash memory ranges
>> to ensure that the memory ranges added to elfcorehdr do not include the
>> hot-removed memory.
>>
>> Memory remove
>> |
>> v
>> Offline pages
>> |
>> v
>> Initiate memory notify call <----> crash hotplug handler
>> chain for MEM_OFFLINE event
>> |
>> v
>> Update memblock list
>>
>> Figure 1
>>
>> There are two system calls, `kexec_file_load` and `kexec_load`, used to
>> load the kdump image. A few changes have been made to ensure that the
>> kernel can safely update the elfcorehdr component of the kdump image for
>> both system calls.
>>
>> For the kexec_file_load syscall, kdump image is prepared in the kernel.
>> To support an increasing number of memory regions, the elfcorehdr is
>> built with extra buffer space to ensure that it can accommodate
>> additional memory ranges in future.
>>
>> For the kexec_load syscall, the elfcorehdr is updated only if the
>> KEXEC_CRASH_HOTPLUG_SUPPORT kexec flag is passed to the kernel by the
>> kexec tool. Passing this flag to the kernel indicates that the
>> elfcorehdr is built to accommodate additional memory ranges and the
>> elfcorehdr segment is not considered for SHA calculation, making it safe
>> to update.
>>
>> The changes related to this feature are kept under the CRASH_HOTPLUG
>> config, and it is enabled by default.
>>
>> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>> Cc: Akhil Raj <lf32.dev@gmail.com>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Aneesh Kumar K.V <aneesh.kumar@kernel.org>
>> Cc: Baoquan He <bhe@redhat.com>
>> Cc: Borislav Petkov (AMD) <bp@alien8.de>
>> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
>> Cc: Dave Hansen <dave.hansen@linux.intel.com>
>> Cc: Dave Young <dyoung@redhat.com>
>> Cc: David Hildenbrand <david@redhat.com>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Cc: Hari Bathini <hbathini@linux.ibm.com>
>> Cc: Laurent Dufour <laurent.dufour@fr.ibm.com>
>> Cc: Mahesh Salgaonkar <mahesh@linux.ibm.com>
>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>> Cc: Mimi Zohar <zohar@linux.ibm.com>
>> Cc: Naveen N Rao <naveen@kernel.org>
>> Cc: Oscar Salvador <osalvador@suse.de>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Valentin Schneider <vschneid@redhat.com>
>> Cc: Vivek Goyal <vgoyal@redhat.com>
>> Cc: kexec@lists.infradead.org
>> Cc: x86@kernel.org
>> ---
>> arch/powerpc/include/asm/kexec.h | 5 +-
>> arch/powerpc/include/asm/kexec_ranges.h | 1 +
>> arch/powerpc/kexec/core_64.c | 107 +++++++++++++++++++++++-
>> arch/powerpc/kexec/file_load_64.c | 34 +++++++-
>> arch/powerpc/kexec/ranges.c | 85 +++++++++++++++++++
>> 5 files changed, 225 insertions(+), 7 deletions(-)
>>
>> diff --git a/arch/powerpc/include/asm/kexec.h
>> b/arch/powerpc/include/asm/kexec.h
>> index 943e58eb9bff..25ff5b7f1a28 100644
>> --- a/arch/powerpc/include/asm/kexec.h
>> +++ b/arch/powerpc/include/asm/kexec.h
>> @@ -116,8 +116,11 @@ int get_crash_memory_ranges(struct crash_mem
>> **mem_ranges);
>> #ifdef CONFIG_CRASH_HOTPLUG
>> void arch_crash_handle_hotplug_event(struct kimage *image, void *arg);
>> #define arch_crash_handle_hotplug_event
>> arch_crash_handle_hotplug_event
>> -#endif /*CONFIG_CRASH_HOTPLUG */
>> +unsigned int arch_crash_get_elfcorehdr_size(void);
>> +#define crash_get_elfcorehdr_size arch_crash_get_elfcorehdr_size
>> +
>> +#endif /*CONFIG_CRASH_HOTPLUG */
>> #endif /* CONFIG_PPC64 */
>> #ifdef CONFIG_KEXEC_FILE
>> diff --git a/arch/powerpc/include/asm/kexec_ranges.h
>> b/arch/powerpc/include/asm/kexec_ranges.h
>> index f83866a19e87..802abf580cf0 100644
>> --- a/arch/powerpc/include/asm/kexec_ranges.h
>> +++ b/arch/powerpc/include/asm/kexec_ranges.h
>> @@ -7,6 +7,7 @@
>> void sort_memory_ranges(struct crash_mem *mrngs, bool merge);
>> struct crash_mem *realloc_mem_ranges(struct crash_mem **mem_ranges);
>> int add_mem_range(struct crash_mem **mem_ranges, u64 base, u64 size);
>> +int remove_mem_range(struct crash_mem **mem_ranges, u64 base, u64
>> size);
>> int add_tce_mem_ranges(struct crash_mem **mem_ranges);
>> int add_initrd_mem_range(struct crash_mem **mem_ranges);
>> #ifdef CONFIG_PPC_64S_HASH_MMU
>> diff --git a/arch/powerpc/kexec/core_64.c b/arch/powerpc/kexec/core_64.c
>> index 43fcd78c2102..4673f150f973 100644
>> --- a/arch/powerpc/kexec/core_64.c
>> +++ b/arch/powerpc/kexec/core_64.c
>> @@ -19,8 +19,11 @@
>> #include <linux/of.h>
>> #include <linux/libfdt.h>
>> #include <linux/memblock.h>
>> +#include <linux/memory.h>
>> #include <asm/page.h>
>> +#include <asm/drmem.h>
>> +#include <asm/mmzone.h>
>> #include <asm/current.h>
>> #include <asm/machdep.h>
>> #include <asm/cacheflush.h>
>> @@ -546,6 +549,101 @@ int update_cpus_node(void *fdt)
>> #undef pr_fmt
>> #define pr_fmt(fmt) "crash hp: " fmt
>> +/*
>> + * Advertise preferred elfcorehdr size to userspace via
>> + * /sys/kernel/crash_elfcorehdr_size sysfs interface.
>> + */
>> +unsigned int arch_crash_get_elfcorehdr_size(void)
>> +{
>> + unsigned int sz;
>> + unsigned long elf_phdr_cnt;
>> +
>> + /* Program header for CPU notes and vmcoreinfo */
>> + elf_phdr_cnt = 2;
>> + if (IS_ENABLED(CONFIG_MEMORY_HOTPLUG))
>> + /* In the worst case, a Phdr is needed for every other LMB
>> to be
>> + * represented as an individual crash range.
>> + */
>> + elf_phdr_cnt += memory_hotplug_max() / (2 * drmem_lmb_size());
>> +
>> + /* Do not cross the max limit */
>> + if (elf_phdr_cnt > PN_XNUM)
>> + elf_phdr_cnt = PN_XNUM;
>> +
>> + sz = sizeof(struct elfhdr) + (elf_phdr_cnt * sizeof(Elf64_Phdr));
>> + return sz;
>> +}
>> +
>> +/**
>> + * update_crash_elfcorehdr() - Recreate the elfcorehdr and replace
>> it with old
>> + * elfcorehdr in the kexec segment array.
>> + * @image: the active struct kimage
>> + * @mn: struct memory_notify data handler
>> + */
>> +static void update_crash_elfcorehdr(struct kimage *image, struct
>> memory_notify *mn)
>> +{
>> + int ret;
>> + struct crash_mem *cmem = NULL;
>> + struct kexec_segment *ksegment;
>> + void *ptr, *mem, *elfbuf = NULL;
>> + unsigned long elfsz, memsz, base_addr, size;
>> +
>> + ksegment = &image->segment[image->elfcorehdr_index];
>> + mem = (void *) ksegment->mem;
>> + memsz = ksegment->memsz;
>> +
>> + ret = get_crash_memory_ranges(&cmem);
>> + if (ret) {
>> + pr_err("Failed to get crash mem range\n");
>> + return;
>> + }
>> +
>> + /*
>> + * The hot unplugged memory is part of crash memory ranges,
>> + * remove it here.
>> + */
>> + if (image->hp_action == KEXEC_CRASH_HP_REMOVE_MEMORY) {
>> + base_addr = PFN_PHYS(mn->start_pfn);
>> + size = mn->nr_pages * PAGE_SIZE;
>> + ret = remove_mem_range(&cmem, base_addr, size);
>> + if (ret) {
>> + pr_err("Failed to remove hot-unplugged from crash memory
>> ranges.\n");
>> + return;
>> + }
>> + }
>> +
>> + ret = crash_prepare_elf64_headers(cmem, false, &elfbuf, &elfsz);
>> + if (ret) {
>> + pr_err("Failed to prepare elf header\n");
>> + return;
>> + }
>> +
>
>
>
>> + /*
>> + * It is unlikely that kernel hit this because elfcorehdr kexec
>> + * segment (memsz) is built with addition space to accommodate
>> growing
>> + * number of crash memory ranges while loading the kdump kernel.
>> It is
>> + * Just to avoid any unforeseen case.
>
> nitpick..
>
> s/Just/just/
Thanks I will fix it.
>
>> + */
>> + if (elfsz > memsz) {
>> + pr_err("Updated crash elfcorehdr elfsz %lu > memsz %lu",
>> elfsz, memsz);
>> + goto out;
>> + }
>> +
>> + ptr = __va(mem);
>> + if (ptr) {
>> + /* Temporarily invalidate the crash image while it is
>> replaced */
>> + xchg(&kexec_crash_image, NULL);
>> +
>> + /* Replace the old elfcorehdr with newly prepared elfcorehdr */
>> + memcpy((void *)ptr, elfbuf, elfsz);
>> +
>> + /* The crash image is now valid once again */
>> + xchg(&kexec_crash_image, image);
>> + }
>> +out:
>> + vfree(elfbuf);
>> +}
>> +
>> /**
>> * arch_crash_handle_hotplug_event - Handle crash CPU/Memory
>> hotplug events to update the
>> * necessary kexec segments based on the
>> hotplug event.
>> @@ -556,7 +654,7 @@ int update_cpus_node(void *fdt)
>> * CPU addition: Update the FDT segment to include the newly added
>> CPU.
>> * CPU removal: No action is needed, with the assumption that it's
>> okay to have offline CPUs
>> * as part of the FDT.
>> - * Memory addition/removal: No action is taken as this is not yet
>> supported.
>> + * Memory addition/removal: Recreate the elfcorehdr segment
>> */
>> void arch_crash_handle_hotplug_event(struct kimage *image, void *arg)
>> {
>> @@ -570,7 +668,6 @@ void arch_crash_handle_hotplug_event(struct
>> kimage *image, void *arg)
>> return;
>
>> } else if (hp_action == KEXEC_CRASH_HP_ADD_CPU) {
>> -
>
>> void *fdt, *ptr;
>> unsigned long mem;
>> int i, fdt_index = -1;
>> @@ -605,8 +702,10 @@ void arch_crash_handle_hotplug_event(struct
>> kimage *image, void *arg)
>
>> } else if (hp_action == KEXEC_CRASH_HP_REMOVE_MEMORY ||
>> hp_action == KEXEC_CRASH_HP_ADD_MEMORY) {
>
>> - pr_info_once("Crash update is not supported for memory
>> hotplug\n");
>> - return;
>> + struct memory_notify *mn;
>> +
>> + mn = (struct memory_notify *)arg;
>> + update_crash_elfcorehdr(image, mn);
>> }
>
> Use switch case statement for hotplug actions for better readability..
Sure.
Thanks,
Sourabh
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>, linuxppc-dev@ozlabs.org
Cc: Valentin Schneider <vschneid@redhat.com>,
x86@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, David Hildenbrand <david@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
kexec@lists.infradead.org, Naveen N Rao <naveen@kernel.org>,
Mimi Zohar <zohar@linux.ibm.com>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
"Aneesh Kumar K . V" <aneesh.kumar@kernel.org>,
Laurent Dufour <laurent.dufour@fr.ibm.com>,
Borislav Petkov <bp@alien8.de>, Akhil Raj <lf32.dev@gmail.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Dave Young <dyoung@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Vivek Goyal <vgoyal@redhat.com>,
Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH v15 5/5] powerpc: add crash memory hotplug support
Date: Mon, 29 Jan 2024 12:16:01 +0530 [thread overview]
Message-ID: <d2996e30-cd3c-461a-8f8f-46dfb8938407@linux.ibm.com> (raw)
In-Reply-To: <bd82e721-e674-4cfe-b9bf-942aaf7ee52c@linux.ibm.com>
On 23/01/24 15:52, Hari Bathini wrote:
>
>
> On 11/01/24 4:21 pm, Sourabh Jain wrote:
>> Extend the arch crash hotplug handler, as introduced by the patch title
>> ("powerpc: add crash CPU hotplug support"), to also support memory
>> add/remove events.
>>
>> Elfcorehdr describes the memory of the crash kernel to capture the
>> kernel; hence, it needs to be updated if memory resources change due to
>> memory add/remove events. Therefore, arch_crash_handle_hotplug_event()
>> is updated to recreate the elfcorehdr and replace it with the previous
>> one on memory add/remove events.
>>
>> The memblock list is used to prepare the elfcorehdr. In the case of
>> memory hot removal, the memblock list is updated after the arch crash
>> hotplug handler is triggered, as depicted in Figure 1. Thus, the
>> hot-removed memory is explicitly removed from the crash memory ranges
>> to ensure that the memory ranges added to elfcorehdr do not include the
>> hot-removed memory.
>>
>> Memory remove
>> |
>> v
>> Offline pages
>> |
>> v
>> Initiate memory notify call <----> crash hotplug handler
>> chain for MEM_OFFLINE event
>> |
>> v
>> Update memblock list
>>
>> Figure 1
>>
>> There are two system calls, `kexec_file_load` and `kexec_load`, used to
>> load the kdump image. A few changes have been made to ensure that the
>> kernel can safely update the elfcorehdr component of the kdump image for
>> both system calls.
>>
>> For the kexec_file_load syscall, kdump image is prepared in the kernel.
>> To support an increasing number of memory regions, the elfcorehdr is
>> built with extra buffer space to ensure that it can accommodate
>> additional memory ranges in future.
>>
>> For the kexec_load syscall, the elfcorehdr is updated only if the
>> KEXEC_CRASH_HOTPLUG_SUPPORT kexec flag is passed to the kernel by the
>> kexec tool. Passing this flag to the kernel indicates that the
>> elfcorehdr is built to accommodate additional memory ranges and the
>> elfcorehdr segment is not considered for SHA calculation, making it safe
>> to update.
>>
>> The changes related to this feature are kept under the CRASH_HOTPLUG
>> config, and it is enabled by default.
>>
>> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>> Cc: Akhil Raj <lf32.dev@gmail.com>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Aneesh Kumar K.V <aneesh.kumar@kernel.org>
>> Cc: Baoquan He <bhe@redhat.com>
>> Cc: Borislav Petkov (AMD) <bp@alien8.de>
>> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> Cc: Christophe Leroy <christophe.leroy@csgroup.eu>
>> Cc: Dave Hansen <dave.hansen@linux.intel.com>
>> Cc: Dave Young <dyoung@redhat.com>
>> Cc: David Hildenbrand <david@redhat.com>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Cc: Hari Bathini <hbathini@linux.ibm.com>
>> Cc: Laurent Dufour <laurent.dufour@fr.ibm.com>
>> Cc: Mahesh Salgaonkar <mahesh@linux.ibm.com>
>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>> Cc: Mimi Zohar <zohar@linux.ibm.com>
>> Cc: Naveen N Rao <naveen@kernel.org>
>> Cc: Oscar Salvador <osalvador@suse.de>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Valentin Schneider <vschneid@redhat.com>
>> Cc: Vivek Goyal <vgoyal@redhat.com>
>> Cc: kexec@lists.infradead.org
>> Cc: x86@kernel.org
>> ---
>> arch/powerpc/include/asm/kexec.h | 5 +-
>> arch/powerpc/include/asm/kexec_ranges.h | 1 +
>> arch/powerpc/kexec/core_64.c | 107 +++++++++++++++++++++++-
>> arch/powerpc/kexec/file_load_64.c | 34 +++++++-
>> arch/powerpc/kexec/ranges.c | 85 +++++++++++++++++++
>> 5 files changed, 225 insertions(+), 7 deletions(-)
>>
>> diff --git a/arch/powerpc/include/asm/kexec.h
>> b/arch/powerpc/include/asm/kexec.h
>> index 943e58eb9bff..25ff5b7f1a28 100644
>> --- a/arch/powerpc/include/asm/kexec.h
>> +++ b/arch/powerpc/include/asm/kexec.h
>> @@ -116,8 +116,11 @@ int get_crash_memory_ranges(struct crash_mem
>> **mem_ranges);
>> #ifdef CONFIG_CRASH_HOTPLUG
>> void arch_crash_handle_hotplug_event(struct kimage *image, void *arg);
>> #define arch_crash_handle_hotplug_event
>> arch_crash_handle_hotplug_event
>> -#endif /*CONFIG_CRASH_HOTPLUG */
>> +unsigned int arch_crash_get_elfcorehdr_size(void);
>> +#define crash_get_elfcorehdr_size arch_crash_get_elfcorehdr_size
>> +
>> +#endif /*CONFIG_CRASH_HOTPLUG */
>> #endif /* CONFIG_PPC64 */
>> #ifdef CONFIG_KEXEC_FILE
>> diff --git a/arch/powerpc/include/asm/kexec_ranges.h
>> b/arch/powerpc/include/asm/kexec_ranges.h
>> index f83866a19e87..802abf580cf0 100644
>> --- a/arch/powerpc/include/asm/kexec_ranges.h
>> +++ b/arch/powerpc/include/asm/kexec_ranges.h
>> @@ -7,6 +7,7 @@
>> void sort_memory_ranges(struct crash_mem *mrngs, bool merge);
>> struct crash_mem *realloc_mem_ranges(struct crash_mem **mem_ranges);
>> int add_mem_range(struct crash_mem **mem_ranges, u64 base, u64 size);
>> +int remove_mem_range(struct crash_mem **mem_ranges, u64 base, u64
>> size);
>> int add_tce_mem_ranges(struct crash_mem **mem_ranges);
>> int add_initrd_mem_range(struct crash_mem **mem_ranges);
>> #ifdef CONFIG_PPC_64S_HASH_MMU
>> diff --git a/arch/powerpc/kexec/core_64.c b/arch/powerpc/kexec/core_64.c
>> index 43fcd78c2102..4673f150f973 100644
>> --- a/arch/powerpc/kexec/core_64.c
>> +++ b/arch/powerpc/kexec/core_64.c
>> @@ -19,8 +19,11 @@
>> #include <linux/of.h>
>> #include <linux/libfdt.h>
>> #include <linux/memblock.h>
>> +#include <linux/memory.h>
>> #include <asm/page.h>
>> +#include <asm/drmem.h>
>> +#include <asm/mmzone.h>
>> #include <asm/current.h>
>> #include <asm/machdep.h>
>> #include <asm/cacheflush.h>
>> @@ -546,6 +549,101 @@ int update_cpus_node(void *fdt)
>> #undef pr_fmt
>> #define pr_fmt(fmt) "crash hp: " fmt
>> +/*
>> + * Advertise preferred elfcorehdr size to userspace via
>> + * /sys/kernel/crash_elfcorehdr_size sysfs interface.
>> + */
>> +unsigned int arch_crash_get_elfcorehdr_size(void)
>> +{
>> + unsigned int sz;
>> + unsigned long elf_phdr_cnt;
>> +
>> + /* Program header for CPU notes and vmcoreinfo */
>> + elf_phdr_cnt = 2;
>> + if (IS_ENABLED(CONFIG_MEMORY_HOTPLUG))
>> + /* In the worst case, a Phdr is needed for every other LMB
>> to be
>> + * represented as an individual crash range.
>> + */
>> + elf_phdr_cnt += memory_hotplug_max() / (2 * drmem_lmb_size());
>> +
>> + /* Do not cross the max limit */
>> + if (elf_phdr_cnt > PN_XNUM)
>> + elf_phdr_cnt = PN_XNUM;
>> +
>> + sz = sizeof(struct elfhdr) + (elf_phdr_cnt * sizeof(Elf64_Phdr));
>> + return sz;
>> +}
>> +
>> +/**
>> + * update_crash_elfcorehdr() - Recreate the elfcorehdr and replace
>> it with old
>> + * elfcorehdr in the kexec segment array.
>> + * @image: the active struct kimage
>> + * @mn: struct memory_notify data handler
>> + */
>> +static void update_crash_elfcorehdr(struct kimage *image, struct
>> memory_notify *mn)
>> +{
>> + int ret;
>> + struct crash_mem *cmem = NULL;
>> + struct kexec_segment *ksegment;
>> + void *ptr, *mem, *elfbuf = NULL;
>> + unsigned long elfsz, memsz, base_addr, size;
>> +
>> + ksegment = &image->segment[image->elfcorehdr_index];
>> + mem = (void *) ksegment->mem;
>> + memsz = ksegment->memsz;
>> +
>> + ret = get_crash_memory_ranges(&cmem);
>> + if (ret) {
>> + pr_err("Failed to get crash mem range\n");
>> + return;
>> + }
>> +
>> + /*
>> + * The hot unplugged memory is part of crash memory ranges,
>> + * remove it here.
>> + */
>> + if (image->hp_action == KEXEC_CRASH_HP_REMOVE_MEMORY) {
>> + base_addr = PFN_PHYS(mn->start_pfn);
>> + size = mn->nr_pages * PAGE_SIZE;
>> + ret = remove_mem_range(&cmem, base_addr, size);
>> + if (ret) {
>> + pr_err("Failed to remove hot-unplugged from crash memory
>> ranges.\n");
>> + return;
>> + }
>> + }
>> +
>> + ret = crash_prepare_elf64_headers(cmem, false, &elfbuf, &elfsz);
>> + if (ret) {
>> + pr_err("Failed to prepare elf header\n");
>> + return;
>> + }
>> +
>
>
>
>> + /*
>> + * It is unlikely that kernel hit this because elfcorehdr kexec
>> + * segment (memsz) is built with addition space to accommodate
>> growing
>> + * number of crash memory ranges while loading the kdump kernel.
>> It is
>> + * Just to avoid any unforeseen case.
>
> nitpick..
>
> s/Just/just/
Thanks I will fix it.
>
>> + */
>> + if (elfsz > memsz) {
>> + pr_err("Updated crash elfcorehdr elfsz %lu > memsz %lu",
>> elfsz, memsz);
>> + goto out;
>> + }
>> +
>> + ptr = __va(mem);
>> + if (ptr) {
>> + /* Temporarily invalidate the crash image while it is
>> replaced */
>> + xchg(&kexec_crash_image, NULL);
>> +
>> + /* Replace the old elfcorehdr with newly prepared elfcorehdr */
>> + memcpy((void *)ptr, elfbuf, elfsz);
>> +
>> + /* The crash image is now valid once again */
>> + xchg(&kexec_crash_image, image);
>> + }
>> +out:
>> + vfree(elfbuf);
>> +}
>> +
>> /**
>> * arch_crash_handle_hotplug_event - Handle crash CPU/Memory
>> hotplug events to update the
>> * necessary kexec segments based on the
>> hotplug event.
>> @@ -556,7 +654,7 @@ int update_cpus_node(void *fdt)
>> * CPU addition: Update the FDT segment to include the newly added
>> CPU.
>> * CPU removal: No action is needed, with the assumption that it's
>> okay to have offline CPUs
>> * as part of the FDT.
>> - * Memory addition/removal: No action is taken as this is not yet
>> supported.
>> + * Memory addition/removal: Recreate the elfcorehdr segment
>> */
>> void arch_crash_handle_hotplug_event(struct kimage *image, void *arg)
>> {
>> @@ -570,7 +668,6 @@ void arch_crash_handle_hotplug_event(struct
>> kimage *image, void *arg)
>> return;
>
>> } else if (hp_action == KEXEC_CRASH_HP_ADD_CPU) {
>> -
>
>> void *fdt, *ptr;
>> unsigned long mem;
>> int i, fdt_index = -1;
>> @@ -605,8 +702,10 @@ void arch_crash_handle_hotplug_event(struct
>> kimage *image, void *arg)
>
>> } else if (hp_action == KEXEC_CRASH_HP_REMOVE_MEMORY ||
>> hp_action == KEXEC_CRASH_HP_ADD_MEMORY) {
>
>> - pr_info_once("Crash update is not supported for memory
>> hotplug\n");
>> - return;
>> + struct memory_notify *mn;
>> +
>> + mn = (struct memory_notify *)arg;
>> + update_crash_elfcorehdr(image, mn);
>> }
>
> Use switch case statement for hotplug actions for better readability..
Sure.
Thanks,
Sourabh
next prev parent reply other threads:[~2024-01-29 6:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 10:51 [PATCH v15 0/5] powerpc/crash: Kernel handling of CPU and memory hotplug Sourabh Jain
2024-01-11 10:51 ` Sourabh Jain
2024-01-11 10:51 ` [PATCH v15 1/5] crash: forward memory_notify arg to arch crash hotplug handler Sourabh Jain
2024-01-11 10:51 ` Sourabh Jain
2024-02-05 3:11 ` Baoquan He
2024-02-05 3:11 ` Baoquan He
2024-02-12 11:57 ` Sourabh Jain
2024-02-12 11:57 ` Sourabh Jain
2024-01-11 10:51 ` [PATCH v15 2/5] crash: add a new kexec flag for hotplug support Sourabh Jain
2024-01-11 10:51 ` Sourabh Jain
2024-02-05 3:10 ` Baoquan He
2024-02-05 3:10 ` Baoquan He
2024-02-12 13:57 ` Sourabh Jain
2024-02-12 13:57 ` Sourabh Jain
2024-02-13 3:21 ` Baoquan He
2024-02-13 3:21 ` Baoquan He
2024-02-14 13:35 ` Sourabh Jain
2024-02-14 13:35 ` Sourabh Jain
2024-01-11 10:51 ` [PATCH v15 3/5] powerpc/kexec: turn some static helper functions public Sourabh Jain
2024-01-11 10:51 ` Sourabh Jain
2024-01-11 10:51 ` [PATCH v15 4/5] powerpc: add crash CPU hotplug support Sourabh Jain
2024-01-11 10:51 ` Sourabh Jain
2024-01-23 10:16 ` Hari Bathini
2024-01-23 10:16 ` Hari Bathini
2024-01-11 10:51 ` [PATCH v15 5/5] powerpc: add crash memory " Sourabh Jain
2024-01-11 10:51 ` Sourabh Jain
2024-01-23 10:22 ` Hari Bathini
2024-01-23 10:22 ` Hari Bathini
2024-01-29 6:46 ` Sourabh Jain [this message]
2024-01-29 6:46 ` 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=d2996e30-cd3c-461a-8f8f-46dfb8938407@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=bhe@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dyoung@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hbathini@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=laurent.dufour@fr.ibm.com \
--cc=lf32.dev@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=naveen@kernel.org \
--cc=osalvador@suse.de \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=vschneid@redhat.com \
--cc=x86@kernel.org \
--cc=zohar@linux.ibm.com \
/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.