From: Eric DeVolder <eric.devolder@oracle.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>,
linuxppc-dev@ozlabs.org, mpe@ellerman.id.au
Cc: mahesh@linux.vnet.ibm.com, kexec@lists.infradead.org,
bhe@redhat.com, hbathini@linux.ibm.com
Subject: Re: [PATCH v5 3/6] crash: add phdr for possible CPUs in elfcorehdr
Date: Tue, 22 Nov 2022 11:58:00 -0600 [thread overview]
Message-ID: <0af5f619-3b39-7118-66c6-ba5b0c85c3dd@oracle.com> (raw)
In-Reply-To: <20221120232508.327554-4-sourabhjain@linux.ibm.com>
On 11/20/22 17:25, Sourabh Jain wrote:
> On architectures like PowerPC the crash notes are available for all
> possible CPUs. So let's populate the elfcorehdr for all possible
> CPUs having crash notes to avoid updating elfcorehdr during in-kernel
> crash update on CPU hotplug events.
>
> The similar technique was used in kexec-tool for kexec_load case.
>
> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
> ---
> kernel/crash_core.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/crash_core.c b/kernel/crash_core.c
> index bca1b198d9e55..f6cccdcadc9f3 100644
> --- a/kernel/crash_core.c
> +++ b/kernel/crash_core.c
> @@ -364,16 +364,19 @@ int crash_prepare_elf64_headers(struct kimage *image, struct crash_mem *mem,
> ehdr->e_ehsize = sizeof(Elf64_Ehdr);
> ehdr->e_phentsize = sizeof(Elf64_Phdr);
>
> - /* Prepare one phdr of type PT_NOTE for each present CPU */
> - for_each_present_cpu(cpu) {
> + /* Prepare one phdr of type PT_NOTE for possible CPU with crash note. */
> + for_each_possible_cpu(cpu) {
> if (IS_ENABLED(CONFIG_HOTPLUG_CPU)) {
> /* Skip the soon-to-be offlined cpu */
> if (image->hotplug_event && (cpu == image->offlinecpu))
> continue;
> }
>
> - phdr->p_type = PT_NOTE;
> notes_addr = per_cpu_ptr_to_phys(per_cpu_ptr(crash_notes, cpu));
> + if (!notes_addr)
> + continue;
> +
> + phdr->p_type = PT_NOTE;
> phdr->p_offset = phdr->p_paddr = notes_addr;
> phdr->p_filesz = phdr->p_memsz = sizeof(note_buf_t);
> (ehdr->e_phnum)++;
>
I did a quick test of this for x86_64 and it works.
Reviewed-by: Eric DeVolder <eric.devolder@oracle.com>
next prev parent reply other threads:[~2022-11-22 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 23:25 [PATCH v5 0/6] In kernel handling of CPU hotplug events for crash kernel Sourabh Jain
2022-11-20 23:25 ` [PATCH v5 1/6] powerpc/kexec: turn some static helper functions public Sourabh Jain
2022-11-20 23:25 ` [PATCH v5 2/6] powerpc/crash: update kimage_arch struct Sourabh Jain
2022-11-20 23:25 ` [PATCH v5 3/6] crash: add phdr for possible CPUs in elfcorehdr Sourabh Jain
2022-11-22 17:58 ` Eric DeVolder [this message]
2022-11-23 15:38 ` Sourabh Jain
2022-11-20 23:25 ` [PATCH v5 4/6] powerpc/crash: add crash CPU hotplug support Sourabh Jain
2022-11-20 23:25 ` [PATCH v5 5/6] crash: forward memory_notify args to arch crash hotplug handler Sourabh Jain
2022-11-22 18:03 ` Eric DeVolder
2022-11-20 23:25 ` [PATCH v5 6/6] powerpc/kexec: add crash memory hotplug support 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=0af5f619-3b39-7118-66c6-ba5b0c85c3dd@oracle.com \
--to=eric.devolder@oracle.com \
--cc=bhe@redhat.com \
--cc=hbathini@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=sourabhjain@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 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).