From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: Michael Bringmann <mwb@linux.vnet.ibm.com>
Cc: ego@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
Nicholas Piggin <npiggin@gmail.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] pseries/hotplug: Add more delay in pseries_cpu_die while waiting for rtas-stop
Date: Mon, 10 Dec 2018 18:31:43 -0200 [thread overview]
Message-ID: <87a7ld3yz4.fsf@morokweng.localdomain> (raw)
In-Reply-To: <06dfb955-6af9-ae23-3919-9bee447cfcdc@linux.vnet.ibm.com>
Hello Michael,
Michael Bringmann <mwb@linux.vnet.ibm.com> writes:
> I have asked Scott Mayes to take a look at one of these crashes from
> the phyp side. I will let you know if he finds anything notable.
Thanks! It might make sense to test whether booting with
cede_offline=off makes the bug go away.
One suspicion I have is regarding the code handling CPU_STATE_INACTIVE.
From what I understand, it is a powerpc-specific CPU state and from the
perspective of the generic CPU hotplug state machine, inactive CPUs are
already fully offline. Which means that the locking performed by the
generic code state machine doesn't apply to transitioning CPUs from
INACTIVE to OFFLINE state. Perhaps the bug is that there is more than
one CPU making that transition at the same time? That would cause two
CPUs to call RTAS stop-self.
I haven't checked whether this is really possible or not, though. It's
just a conjecture.
--
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2018-12-10 20:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 11:31 [PATCH] pseries/hotplug: Add more delay in pseries_cpu_die while waiting for rtas-stop Gautham R. Shenoy
2018-12-06 17:28 ` Thiago Jung Bauermann
2018-12-07 10:43 ` Gautham R Shenoy
2018-12-07 12:03 ` Gautham R Shenoy
2018-12-08 2:40 ` Thiago Jung Bauermann
2018-12-10 20:16 ` Michael Bringmann
2018-12-10 20:31 ` Thiago Jung Bauermann [this message]
2018-12-11 22:11 ` Michael Bringmann
2019-01-09 6:08 ` Gautham R Shenoy
2019-01-14 18:11 ` Michael Bringmann
2019-01-17 6:03 ` Gautham R Shenoy
2022-07-07 9:51 ` Christophe Leroy
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=87a7ld3yz4.fsf@morokweng.localdomain \
--to=bauerman@linux.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mwb@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--cc=tyreld@linux.vnet.ibm.com \
/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