From: Li Zefan <lizf@cn.fujitsu.com>
To: Peter Zijlstra <peterz@infradead.org>
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: Fri, 04 Mar 2011 10:07:25 +0800 [thread overview]
Message-ID: <4D70495D.8010403@cn.fujitsu.com> (raw)
In-Reply-To: <1299161840.1310.54.camel@laptop>
Peter Zijlstra wrote:
> On Thu, 2011-03-03 at 11:06 +0100, Peter Zijlstra wrote:
>>
>>> list_add_event() is called with spin lock ctl->lock held, while
>>> jump_label_inc() will acquire jump_label_mutex..
>>
>
> The below seems to actually work, I totally overlooked the dec case
> earlier.
>
Yes, it works. Thanks!
prev parent reply other threads:[~2011-03-04 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 8:31 [BUG] lock issue in perf cgroup with jump label enabled Li Zefan
2011-03-03 10:06 ` Peter Zijlstra
2011-03-03 14:17 ` Peter Zijlstra
2011-03-04 2:07 ` Li Zefan [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=4D70495D.8010403@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=eranian@google.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--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