From: Peter Zijlstra <peterz@infradead.org>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Stephane Eranian <eranian@google.com>,
Ingo Molnar <mingo@elte.hu>, Jason Baron <jbaron@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] lock issue in perf cgroup with jump label enabled
Date: Thu, 03 Mar 2011 11:06:27 +0100 [thread overview]
Message-ID: <1299146787.1310.41.camel@laptop> (raw)
In-Reply-To: <4D6F51C9.3020800@cn.fujitsu.com>
On Thu, 2011-03-03 at 16:31 +0800, Li Zefan wrote:
> With CONFIG_JUMP_LABEL enabled:
>
> # mount -t cgroup -o perf_event xxx /mnt
> # mkdir /mnt/test
> # ./perf stat -B -a -e cycles:u -G test -- sleep 1
>
> lockdep warning will be triggered immediately, and the machine
> will become unresponsive.
>
> I guess this is the culprit?
>
> In the "perf cgroup support" patch:
>
> @@ -419,6 +781,17 @@ list_add_event(struct perf_event *event, struct perf_event_con
> list_add_tail(&event->group_entry, list);
> }
>
> + if (is_cgroup_event(event)) {
> + ctx->nr_cgroups++;
> + /*
> + * one more event:
> + * - that has cgroup constraint on event->cpu
> + * - that may need work on context switch
> + */
> + atomic_inc(&per_cpu(perf_cgroup_events, event->cpu));
> + jump_label_inc(&perf_sched_events);
> + }
>
> list_add_event() is called with spin lock ctl->lock held, while
> jump_label_inc() will acquire jump_label_mutex..
I think something like the below ought to cure that.
---
kernel/perf_event.c | 20 +++++++++++---------
1 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/kernel/perf_event.c b/kernel/perf_event.c
index 64a018e..6bc69a4 100644
--- a/kernel/perf_event.c
+++ b/kernel/perf_event.c
@@ -817,16 +817,8 @@ list_add_event(struct perf_event *event, struct perf_event_context *ctx)
list_add_tail(&event->group_entry, list);
}
- if (is_cgroup_event(event)) {
+ if (is_cgroup_event(event))
ctx->nr_cgroups++;
- /*
- * one more event:
- * - that has cgroup constraint on event->cpu
- * - that may need work on context switch
- */
- atomic_inc(&per_cpu(perf_cgroup_events, event->cpu));
- jump_label_inc(&perf_sched_events);
- }
list_add_rcu(&event->event_entry, &ctx->event_list);
if (!ctx->nr_events)
@@ -6553,6 +6545,16 @@ SYSCALL_DEFINE5(perf_event_open,
goto err_context;
}
+ if (is_cgroup_event(event)) {
+ /*
+ * one more event:
+ * - that has cgroup constraint on event->cpu
+ * - that may need work on context switch
+ */
+ atomic_inc(&per_cpu(perf_cgroup_events, event->cpu));
+ jump_label_inc(&perf_sched_events);
+ }
+
if (move_group) {
struct perf_event_context *gctx = group_leader->ctx;
next prev parent reply other threads:[~2011-03-03 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 8:31 Li Zefan
2011-03-03 10:06 ` Peter Zijlstra [this message]
2011-03-03 14:17 ` Peter Zijlstra
2011-03-04 2:07 ` Li Zefan
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=1299146787.1310.41.camel@laptop \
--to=peterz@infradead.org \
--cc=eranian@google.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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®