From: Thomas Gleixner <tglx@linutronix.de>
To: Tvrtko Ursulin <tursulin@ursulin.net>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: Possible bug in CPU hotplug handling (4.14.0-rc5)
Date: Fri, 20 Oct 2017 20:14:24 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1710202012280.2194@nanos> (raw)
In-Reply-To: <64e7e66f-a90b-eaa8-de70-51a8d907b5b4@ursulin.net>
On Fri, 20 Oct 2017, Tvrtko Ursulin wrote:
> Hi all,
>
> I think I've found in bug in the CPU hotplug handling when multi-instance
> states are used. That is in the 4.14.0-rc5 kernel.
> I have not attempted to get to the bottom of the issue to propose an actual
> fix, since the logic there looks somewhat complex, but thought to first
> seek opinion of the people in the know regarding this area.
These commits fiddled with that post rc1, so it's probably burried
somewhere there.
1db49484f21e ("smp/hotplug: Hotplug state fail injection")
5ebe7742fff8 ("smp/hotplug: Differentiate the AP completion between up and down")
5f4b55e10645 ("smp/hotplug: Differentiate the AP-work lockdep class between up and down")
724a86881d03 ("smp/hotplug: Callback vs state-machine consistency")
4dddfb5faa61 ("smp/hotplug: Rewrite AP state machine core")
96abb968549c ("smp/hotplug: Allow external multi-instance rollback")
I'll have a look at it on sunday (tomorrow I'm conferencing) with Peter, so
we should be able to figure it out, unless you beat us to it.
Thanks,
tglx
prev parent reply other threads:[~2017-10-20 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 17:37 Possible bug in CPU hotplug handling (4.14.0-rc5) Tvrtko Ursulin
2017-10-20 18:14 ` Thomas Gleixner [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=alpine.DEB.2.20.1710202012280.2194@nanos \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tursulin@ursulin.net \
/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