From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>,
linux-kernel@vger.kernel.org, h.mitake@gmail.com,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jens Axboe <jens.axboe@oracle.com>,
Jason Baron <jbaron@redhat.com>
Subject: Re: [PATCH RFC 00/11] lock monitor: Separate features related to lock
Date: Tue, 23 Mar 2010 16:45:34 +0100 [thread overview]
Message-ID: <1269359134.5109.93.camel@twins> (raw)
In-Reply-To: <20100317153858.GA5059@nowhere>
On Wed, 2010-03-17 at 16:39 +0100, Frederic Weisbecker wrote:
>
> might_lock_read() uses might_fault(), rcu, workqueues and probably
> yet some others use sequences of lock_acquire/lock_release to prove
> locking while there is actually no real lock operation involved, but
> this is to detect dependency/balance mistakes.
might_fault() simply always takes the mmap_sem because actually hitting
the fault path (which otherwise would establish that relation) is very
rare for some cases, so by forcing that dependency we get better
coverage.
rcu_read_lock() is an actual lock :-)
workqueues use 'fake' locks to connect lock chains to flush, so that we
can detect things like trying to flush a workqueue while holding a lock
that is required to complete the work.
next prev parent reply other threads:[~2010-03-23 15:45 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 10:38 [PATCH RFC 00/11] lock monitor: Separate features related to lock Hitoshi Mitake
2010-03-14 10:38 ` [PATCH RFC 01/11] lock monitor: New subsystem for lock event hooking Hitoshi Mitake
2010-03-14 10:38 ` [PATCH RFC 02/11] Adopt lockdep to lock monitor Hitoshi Mitake
2010-03-14 10:38 ` [PATCH RFC 03/11] Adopt spinlock " Hitoshi Mitake
2010-03-14 10:38 ` [PATCH RFC 04/11] Adopt rwlock " Hitoshi Mitake
2010-03-14 10:38 ` [PATCH RFC 05/11] Adopt arch dependent rwsem " Hitoshi Mitake
2010-03-14 10:38 ` [PATCH RFC 06/11] Adopt rwsem of x86 " Hitoshi Mitake
2010-03-14 10:38 ` [PATCH RFC 07/11] Adopt the way of initializing semaphore " Hitoshi Mitake
2010-03-14 10:38 ` [PATCH RFC 08/11] Adopt mutex " Hitoshi Mitake
2010-03-14 10:38 ` [PATCH RFC 09/11] Adopt rcu_read_lock() " Hitoshi Mitake
2010-03-14 10:38 ` [PATCH RFC 10/11] Adopt kernel/sched.c " Hitoshi Mitake
2010-03-14 10:38 ` [PATCH RFC 11/11] Very dirty temporal solution for testing " Hitoshi Mitake
2010-03-14 18:13 ` [PATCH RFC 00/11] lock monitor: Separate features related to lock Peter Zijlstra
2010-03-17 1:32 ` Frederic Weisbecker
2010-03-17 7:30 ` Hitoshi Mitake
2010-03-17 15:39 ` Frederic Weisbecker
2010-03-18 5:49 ` Hitoshi Mitake
2010-03-18 20:30 ` Frederic Weisbecker
2010-03-20 5:51 ` Hitoshi Mitake
2010-03-23 15:45 ` Peter Zijlstra [this message]
2010-03-17 9:52 ` Ingo Molnar
2010-03-17 13:59 ` Jason Baron
2010-03-18 5:59 ` Hitoshi Mitake
2010-03-18 21:16 ` Frederic Weisbecker
2010-03-19 1:08 ` Mathieu Desnoyers
2010-03-19 1:23 ` Frederic Weisbecker
2010-03-19 1:36 ` Mathieu Desnoyers
2010-03-19 2:27 ` Frederic Weisbecker
2010-03-19 2:40 ` Mathieu Desnoyers
2010-03-19 3:06 ` Frederic Weisbecker
2010-03-19 12:56 ` Mathieu Desnoyers
2010-03-19 16:00 ` Jason Baron
2010-03-20 4:51 ` Frederic Weisbecker
2010-03-20 4:46 ` Frederic Weisbecker
2010-03-20 5:56 ` Hitoshi Mitake
2010-03-20 8:23 ` Hitoshi Mitake
2010-03-21 9:49 ` Hitoshi Mitake
2010-03-23 15:32 ` Peter Zijlstra
2010-04-04 7:56 ` Hitoshi Mitake
2010-03-17 1:47 ` Frederic Weisbecker
2010-03-17 7:33 ` Hitoshi Mitake
2010-03-17 9:50 ` Ingo Molnar
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=1269359134.5109.93.camel@twins \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=h.mitake@gmail.com \
--cc=jbaron@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=paulus@samba.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