linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hari Bathini <hbathini@linux.ibm.com>
To: Eddie James <eajames@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
	christophe.leroy@csgroup.eu, naveen@kernel.org
Subject: Re: [PATCH v2] powerpc/crash: Fix non-smp kexec preparation
Date: Mon, 17 Feb 2025 12:03:46 +0530	[thread overview]
Message-ID: <76aa0eb7-3e74-4087-ab70-6fde4646b008@linux.ibm.com> (raw)
In-Reply-To: <20250211162054.857762-1-eajames@linux.ibm.com>

Hi Eddie,

On 11/02/25 9:50 pm, Eddie James wrote:
> In non-smp configurations, crash_kexec_prepare is never called in
> the crash shutdown path. One result of this is that the crashing_cpu
> variable is never set, preventing crash_save_cpu from storing the
> NT_PRSTATUS elf note in the core dump.
> 

Thanks for fixing this.
Looks good to me.

Reviewed-by: Hari Bathini <hbathini@linux.ibm.com>

> Fixes: c7255058b543 ("powerpc/crash: save cpu register data in crash_smp_send_stop()")
> Signed-off-by: Eddie James <eajames@linux.ibm.com>
> ---
> Changes since v1:
>   - Use if (IS_ENABLED(CONFIG_SMP)) instead of #ifdef CONFIG_SMP
> 
>   arch/powerpc/kexec/crash.c | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/powerpc/kexec/crash.c b/arch/powerpc/kexec/crash.c
> index 9ac3266e49652..a325c1c02f96d 100644
> --- a/arch/powerpc/kexec/crash.c
> +++ b/arch/powerpc/kexec/crash.c
> @@ -359,7 +359,10 @@ void default_machine_crash_shutdown(struct pt_regs *regs)
>   	if (TRAP(regs) == INTERRUPT_SYSTEM_RESET)
>   		is_via_system_reset = 1;
>   
> -	crash_smp_send_stop();
> +	if (IS_ENABLED(CONFIG_SMP))
> +		crash_smp_send_stop();
> +	else
> +		crash_kexec_prepare();
>   
>   	crash_save_cpu(regs, crashing_cpu);
>   



  reply	other threads:[~2025-02-17  6:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11 16:20 [PATCH v2] powerpc/crash: Fix non-smp kexec preparation Eddie James
2025-02-17  6:33 ` Hari Bathini [this message]
2025-05-04  3:21 ` Madhavan Srinivasan

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=76aa0eb7-3e74-4087-ab70-6fde4646b008@linux.ibm.com \
    --to=hbathini@linux.ibm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=eajames@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=naveen@kernel.org \
    --cc=npiggin@gmail.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).