From: Baoquan He <bhe@redhat.com>
To: "Paul E. McKenney" <paulmck@kernel.org>, eric.devolder@oracle.com
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
sfr@canb.auug.org.au, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, sourabhjain@linux.ibm.com, hbathini@linux.ibm.com
Subject: Re: [BUG resend next-20230818] error: 'prepare_elf_headers' defined but not used
Date: Sat, 19 Aug 2023 21:04:33 +0800 [thread overview]
Message-ID: <ZOC94WelqfS0vsFK@MiWiFi-R3L-srv> (raw)
In-Reply-To: <4a991983-da2e-4fcd-965c-5b65de6700da@paulmck-laptop>
On 08/18/23 at 07:28pm, Paul E. McKenney wrote:
> Hello!
>
> This morning's rcutorture testing on next-20230818 complained about
> prepare_elf_headers() being defined but unused on several rcutorture
> scenarios. The patch below makes rcutorture happy, but might or might
> not be a proper fix.
>
> This is a resend adding a few more people on CC, given a possible
> relationship to 9f1f399ca999 ("x86/crash: add x86 crash hotplug support").
>
> Thoughts?
>
Thanks for reporting this, Paul.
>
> ------------------------------------------------------------------------
>
> diff --git a/arch/x86/kernel/crash.c b/arch/x86/kernel/crash.c
> index 1d0f824559fce..926c39e22387b 100644
> --- a/arch/x86/kernel/crash.c
> +++ b/arch/x86/kernel/crash.c
> @@ -127,7 +127,8 @@ void native_machine_crash_shutdown(struct pt_regs *regs)
> crash_save_cpu(regs, safe_smp_processor_id());
> }
>
> -#if defined(CONFIG_KEXEC_FILE) || defined(CONFIG_CRASH_DUMP)
> +#if (defined(CONFIG_KEXEC_FILE) || defined(CONFIG_CRASH_DUMP)) && defined(CONFIG_SMP) && defined(CONFIG_X86_LOCAL_APIC)
Hi Eric,
Now prepare_elf_headers() is needed for kexec_file_load and crash
hotplug support of kexec_load, change it like this?
#if defined(CONFIG_KEXEC_FILE) || defined(CONFIG_CRASH_HOTPLUG)
next prev parent reply other threads:[~2023-08-19 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 18:07 [BUG next-20230818] error: 'prepare_elf_headers' defined but not used Paul E. McKenney
2023-08-19 2:28 ` [BUG resend " Paul E. McKenney
2023-08-19 13:03 ` Eric DeVolder
2023-08-19 20:51 ` Paul E. McKenney
2023-08-19 13:04 ` Baoquan He [this message]
2023-08-19 21:01 ` Paul E. McKenney
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=ZOC94WelqfS0vsFK@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eric.devolder@oracle.com \
--cc=hbathini@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sourabhjain@linux.ibm.com \
--cc=tglx@linutronix.de \
--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 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.