From: Peter Zijlstra <peterz@infradead.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [perf] lockdep warning between cpu_add_remove_lock and &dev->mutex.
Date: Mon, 23 Jan 2023 12:41:29 +0100 [thread overview]
Message-ID: <Y85yadQes4fSwCZm@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <8c3fc3d1-8fed-be22-e0e7-ef1e1ea723ce@I-love.SAKURA.ne.jp>
On Mon, Jan 23, 2023 at 07:39:24PM +0900, Tetsuo Handa wrote:
> Hello.
>
> I tried to apply below patch, and hit lockdep warning during boot.
> Can you break this dependency?
cpu_add_remove_lock
cpu_hotplug_lock
pmus_lock
dev->mutex (pmu_dev_alloc)
vs
dev->mutex
cpu_add_remove_lock (pci_device_probe)
Possibly something like this might do -- I'm not entirely sure it's
fully correct, needs a bit of auditing.
---
diff --git a/kernel/events/core.c b/kernel/events/core.c
index eacc3702654d..d6b2265a9982 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -13570,9 +13570,9 @@ static void perf_event_exit_cpu_context(int cpu)
{
struct perf_cpu_context *cpuctx;
struct perf_event_context *ctx;
+ int idx = srcu_read_lock(&pmus_srcu);
// XXX simplify cpuctx->online
- mutex_lock(&pmus_lock);
cpuctx = per_cpu_ptr(&perf_cpu_context, cpu);
ctx = &cpuctx->ctx;
@@ -13581,7 +13581,7 @@ static void perf_event_exit_cpu_context(int cpu)
cpuctx->online = 0;
mutex_unlock(&ctx->mutex);
cpumask_clear_cpu(cpu, perf_online_mask);
- mutex_unlock(&pmus_lock);
+ srcu_read_unlock(&pmus_srcu, idx);
}
#else
@@ -13593,10 +13594,11 @@ int perf_event_init_cpu(unsigned int cpu)
{
struct perf_cpu_context *cpuctx;
struct perf_event_context *ctx;
+ int idx;
perf_swevent_init_cpu(cpu);
- mutex_lock(&pmus_lock);
+ idx = srcu_read_lock(&pmus_srcu);
cpumask_set_cpu(cpu, perf_online_mask);
cpuctx = per_cpu_ptr(&perf_cpu_context, cpu);
ctx = &cpuctx->ctx;
@@ -13604,7 +13606,7 @@ int perf_event_init_cpu(unsigned int cpu)
mutex_lock(&ctx->mutex);
cpuctx->online = 1;
mutex_unlock(&ctx->mutex);
- mutex_unlock(&pmus_lock);
+ srcu_read_unlock(&pmus_srcu, idx);
return 0;
}
next prev parent reply other threads:[~2023-01-23 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 10:39 Tetsuo Handa
2023-01-23 11:41 ` Peter Zijlstra [this message]
2023-01-23 14:10 ` Tetsuo Handa
2023-01-23 15:02 ` Peter Zijlstra
2023-01-23 15:28 ` Peter Zijlstra
[not found] ` <20230124095424.4448-1-hdanton@sina.com>
2023-01-24 11:16 ` Tetsuo Handa
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=Y85yadQes4fSwCZm@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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®