From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] x86/smpboot: Unbreak CPU0 hotplug
Date: Fri, 30 Jun 2017 10:25:36 +0200 [thread overview]
Message-ID: <87fuehvq4f.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20170626163635.28808-1-vkuznets@redhat.com> (Vitaly Kuznetsov's message of "Mon, 26 Jun 2017 18:36:35 +0200")
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.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> ---
> RFC part: I tested the fix on KVM and Xen guests and it works just fine
> but CPU0 hotplug is not something I'm really familiar with, I may be
> missing some important details. I also skipped code archeology to figure
> out when things got broken.
Any comments? This can be considered as non-RFC if not :-)
--
Vitaly
prev parent reply other threads:[~2017-06-30 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 16:36 [PATCH RFC] x86/smpboot: Unbreak CPU0 hotplug Vitaly Kuznetsov
2017-06-30 8:25 ` Vitaly Kuznetsov [this message]
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=87fuehvq4f.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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.