From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: Daniel Black <daniel.black@au1.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
Subject: Re: powerpc: Drop lockdep_assert_cpus_held call from arch_update_cpu_topology
Date: Thu, 12 Oct 2017 11:20:11 +1100 (AEDT) [thread overview]
Message-ID: <3yCBLz4n8zz9t2Z@ozlabs.org> (raw)
In-Reply-To: <20171005000430.8080-1-bauerman@linux.vnet.ibm.com>
On Thu, 2017-10-05 at 00:04:30 UTC, Thiago Jung Bauermann wrote:
> It turns out that not all paths calling arch_update_cpu_topology hold
> cpu_hotplug_lock, but that's ok because those paths aren't supposed to race
> with any concurrent hotplug events.
>
> Callers of arch_update_cpu_topology are expected to know what they are
> doing when they call the function without holding the lock, so remove the
> lockdep warning.
...
>
> Signed-off-by: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
> Fixes: 3e401f7a2e51 ("powerpc: Only obtain cpu_hotplug_lock if called by rtasd")
> Link: https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-September/163244.html
> Link: https://github.com/linuxppc/linux/issues/106
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/6b2c08f989250c54f31b53dba9ace8
cheers
prev parent reply other threads:[~2017-10-12 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 0:04 [PATCH] powerpc: Drop lockdep_assert_cpus_held call from arch_update_cpu_topology Thiago Jung Bauermann
2017-10-05 12:38 ` Thomas Gleixner
2017-10-05 18:26 ` Thiago Jung Bauermann
2017-10-05 18:46 ` Thomas Gleixner
2017-10-10 9:48 ` Michael Ellerman
2017-10-12 0:20 ` Michael Ellerman [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=3yCBLz4n8zz9t2Z@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=bauerman@linux.vnet.ibm.com \
--cc=daniel.black@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).