From: Peter Zijlstra <peterz@infradead.org>
To: Neeraj Upadhyay <neeraju@codeaurora.org>
Cc: tglx@linutronix.de, josh@joshtriplett.org, mingo@kernel.org,
jiangshanlai@gmail.com, dzickus@redhat.com,
brendan.jackman@arm.com, malat@debian.org, mojha@codeaurora.org,
linux-kernel@vger.kernel.org, sramana@codeaurora.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] cpu/hotplug: Fix acquire of st->should_run in cpuhp_thread_fun()
Date: Wed, 5 Sep 2018 10:12:39 +0200 [thread overview]
Message-ID: <20180905081239.GQ24124@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1536126727-11629-1-git-send-email-neeraju@codeaurora.org>
On Wed, Sep 05, 2018 at 11:22:07AM +0530, Neeraj Upadhyay wrote:
> The smp_mb() in cpuhp_thread_fun() appears to be misplaced, and
> need to be after the load of st->should_run, to prevent
> reordering of the later load/stores w.r.t. the load of
> st->should_run.
I'm tempted to say this changelog needs improvement, but given the
comment that goes with the smp_mb(), yes this is obviously right.
Acked-by: Peter Zijlstra (Intel) <peterz@infraded.org>
> Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
> ---
> kernel/cpu.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/cpu.c b/kernel/cpu.c
> index aa7fe85..eb4041f 100644
> --- a/kernel/cpu.c
> +++ b/kernel/cpu.c
> @@ -607,15 +607,15 @@ static void cpuhp_thread_fun(unsigned int cpu)
> bool bringup = st->bringup;
> enum cpuhp_state state;
>
> + if (WARN_ON_ONCE(!st->should_run))
> + return;
> +
> /*
> * ACQUIRE for the cpuhp_should_run() load of ->should_run. Ensures
> * that if we see ->should_run we also see the rest of the state.
> */
> smp_mb();
>
> - if (WARN_ON_ONCE(!st->should_run))
> - return;
> -
> cpuhp_lock_acquire(bringup);
>
> if (st->single) {
next prev parent reply other threads:[~2018-09-05 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 5:52 Neeraj Upadhyay
2018-09-05 8:12 ` Peter Zijlstra [this message]
2018-09-06 13:51 ` [tip:smp/urgent] cpu/hotplug: Adjust misplaced smb() " tip-bot for Neeraj Upadhyay
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=20180905081239.GQ24124@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=brendan.jackman@arm.com \
--cc=dzickus@redhat.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malat@debian.org \
--cc=mingo@kernel.org \
--cc=mojha@codeaurora.org \
--cc=neeraju@codeaurora.org \
--cc=sramana@codeaurora.org \
--cc=tglx@linutronix.de \
/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®