From: Juergen Gross <jgross@suse.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sstabellini@kernel.org" <sstabellini@kernel.org>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: objtool warning for next-20221118
Date: Fri, 25 Nov 2022 06:30:35 +0100 [thread overview]
Message-ID: <d047c478-d905-7022-0caa-c9b7b0780823@suse.com> (raw)
In-Reply-To: <20221124163928.dof5ldfer6rswlnx@treble>
[-- Attachment #1.1.1: Type: text/plain, Size: 2769 bytes --]
On 24.11.22 17:39, Josh Poimboeuf wrote:
> On Thu, Nov 24, 2022 at 08:47:47AM +0100, Juergen Gross wrote:
>>>> +++ b/arch/x86/xen/smp_pv.c
>>>> @@ -385,17 +385,9 @@ static void xen_pv_play_dead(void) /* used only
>>>> with HOTPLUG_CPU */
>>>> {
>>>> play_dead_common();
>>>> HYPERVISOR_vcpu_op(VCPUOP_down, xen_vcpu_nr(smp_processor_id()), NULL);
>>>> - cpu_bringup();
>>>> - /*
>>>> - * commit 4b0c0f294 (tick: Cleanup NOHZ per cpu data on cpu down)
>>>> - * clears certain data that the cpu_idle loop (which called us
>>>> - * and that we return from) expects. The only way to get that
>>>> - * data back is to call:
>>>> - */
>>>> - tick_nohz_idle_enter();
>>>> - tick_nohz_idle_stop_tick_protected();
>>>> - cpuhp_online_idle(CPUHP_AP_ONLINE_IDLE);
>>>> + /* FIXME: converge cpu_bringup_and_idle() and start_secondary() */
>>>> + cpu_bringup_and_idle();
>>>
>>> I think this will leak stack memory. Multiple cpu offline/online cycles of
>>> the same cpu will finally exhaust the idle stack.
>
> Doh! Of course...
>
> I was actually thinking ahead, to where eventually xen_pv_play_dead()
> can call start_cpu0(), which can be changed to automatically reset the
> stack pointer like this:
>
> SYM_CODE_START(start_cpu0)
> ANNOTATE_NOENDBR
> UNWIND_HINT_EMPTY
> movq PER_CPU_VAR(pcpu_hot + X86_top_of_stack), %rax
> leaq -PTREGS_SIZE(%rax), %rsp
> jmp .Ljump_to_C_code
> SYM_CODE_END(start_cpu0)
>
> but that would only be possible be after more cleanups which converge
> cpu_bringup_and_idle() with start_secondary().
>
>> The attached patch seems to work fine.
>
> The patch looks good to me.
>
> It doesn't solve Paul's original issue where arch_cpu_idle_dead() needs
> to be __noreturn. But that should probably be a separate patch anyway.
Okay, I'll split this off.
>
>> The __noreturn annotation seems to trigger an objtool warning, though, in
>> spite of the added BUG() at the end of xen_pv_play_dead():
>>
>> arch/x86/xen/smp_pv.o: warning: objtool: xen_pv_play_dead() falls through to
>> next function xen_pv_cpu_die()
>
> You'll need to tell objtool that xen_cpu_bringup_again() is noreturn by
> adding "xen_cpu_bringup_again" to global_noreturns[] in
> tools/objtool/check.c.
Ah, okay. Will do that.
> (Yes it's a pain, I'll be working an improved solution to the noreturn
> thing...)
Should be fairly easy, no?
"Just" extend the __noreturn macro to put the function into a ".text.noreturn"
section, which can be handled in a special way by objtool. This would need
an __init_noreturn macro, of course, for a ".init.text.noreturn" section.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3149 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2022-11-25 5:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 4:07 Paul E. McKenney
2022-11-21 11:31 ` Peter Zijlstra
2022-11-21 14:52 ` Paul E. McKenney
2022-11-22 5:16 ` Josh Poimboeuf
2022-11-22 8:35 ` Peter Zijlstra
2022-11-23 0:22 ` Paul E. McKenney
2022-11-23 1:48 ` Josh Poimboeuf
2022-11-23 17:49 ` Paul E. McKenney
2022-11-23 18:19 ` Josh Poimboeuf
2022-11-23 19:12 ` Paul E. McKenney
2022-11-23 22:32 ` Josh Poimboeuf
2022-11-23 23:06 ` Paul E. McKenney
2023-01-28 19:06 ` Paul E. McKenney
2023-02-01 0:02 ` Josh Poimboeuf
2023-02-01 0:33 ` Paul E. McKenney
2023-02-01 4:21 ` Paul E. McKenney
2022-11-23 1:23 ` Josh Poimboeuf
2022-11-23 8:55 ` Peter Zijlstra
2022-11-23 10:52 ` Andrew Cooper
2022-11-23 17:03 ` Josh Poimboeuf
2022-11-24 2:39 ` Josh Poimboeuf
2022-11-24 5:28 ` Juergen Gross
2022-11-24 7:47 ` Juergen Gross
2022-11-24 16:39 ` Josh Poimboeuf
2022-11-25 5:30 ` Juergen Gross [this message]
2022-11-29 19:56 ` Paul E. McKenney
2022-12-02 0:27 ` 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=d047c478-d905-7022-0caa-c9b7b0780823@suse.com \
--to=jgross@suse.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®