From: Ingo Molnar <mingo@kernel.org>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH RESEND] x86/smpboot: Unbreak CPU0 hotplug
Date: Thu, 10 Aug 2017 16:23:52 +0200 [thread overview]
Message-ID: <20170810142351.b7h6usaou66aoywm@gmail.com> (raw)
In-Reply-To: <87fucztyww.fsf@vitty.brq.redhat.com>
* Vitaly Kuznetsov <vkuznets@redhat.com> wrote:
> Vitaly Kuznetsov <vkuznets@redhat.com> writes:
>
> > A hang on CPU0 onlining after a preceding offlining is observed. Trace
> > shows that CPU0 is stuck in check_tsc_sync_target() waiting for source
> > CPU to run check_tsc_sync_source() but this never happens. Source CPU,
> > in its turn, is stuck on synchronize_sched() which is called from
> > native_cpu_up() -> do_boot_cpu() -> unregister_nmi_handler().
> >
> > Fix the issue by moving unregister_nmi_handler() from do_boot_cpu() to
> > native_cpu_up() after cpu onlining is done.
Looks like a classic ABBA deadlock, due to the use of synchronize_sched() in
unregister_nmi_handler(), right?
> >
> > Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> > ---
> > It's been awile since my v1 submission, no comments so far. Resending.
>
> Sorry, but
>
> ping?
>
> I haven't received a single comment on this since the initial submission
> on June, 26 - is it so bad? :-)
So the fix looks good to me at first sight, but wanted to wait for Thomas to ack
it - once he gets back from vacation.
Thanks,
Ingo
next prev parent reply other threads:[~2017-08-10 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 10:58 Vitaly Kuznetsov
2017-08-10 12:01 ` Vitaly Kuznetsov
2017-08-10 14:23 ` Ingo Molnar [this message]
2017-08-10 14:56 ` Vitaly Kuznetsov
2017-08-14 7:09 ` Thomas Gleixner
2017-08-10 16:39 ` [tip:x86/urgent] " tip-bot for Vitaly Kuznetsov
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=20170810142351.b7h6usaou66aoywm@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--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 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®