From: Peter Zijlstra <peterz@infradead.org>
To: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH 0/5] lockdep: Add information of file and line to lockdep_map
Date: Mon, 18 Jan 2010 08:20:19 +0100 [thread overview]
Message-ID: <1263799219.4283.0.camel@laptop> (raw)
In-Reply-To: <4B51B8A4.7010503@dcl.info.waseda.ac.jp>
On Sat, 2010-01-16 at 22:01 +0900, Hitoshi Mitake wrote:
>
> And I want lockdep_map to have another thing, type of lock.
> For example, mutex and spinlock has completely different acquired
> time
> and attributes,
> so I want to separate these things. If lockdep_map has member
> to express type, things will be easy.
I'm worrying about growing things too much.. esp. when the gain is
dubious. People will see the type soon enough when they go look at the
code.
next prev parent reply other threads:[~2010-01-18 7:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 3:28 [PATCH 1/2] perf: Add util/include/linuxhash.h to include hash.h of kernel Hitoshi Mitake
2009-12-16 3:28 ` [PATCH 2/2] perf lock: Fix output of tracing lock events Hitoshi Mitake
2009-12-16 8:19 ` [tip:perf/lock] " tip-bot for Hitoshi Mitake
2009-12-17 8:50 ` [PATCH 2/2] " Ingo Molnar
2009-12-17 9:24 ` Peter Zijlstra
2009-12-17 10:09 ` Ingo Molnar
2009-12-17 10:26 ` Peter Zijlstra
2009-12-17 10:51 ` Ingo Molnar
2009-12-26 13:43 ` Hitoshi Mitake
2009-12-28 10:01 ` Peter Zijlstra
2009-12-31 13:24 ` Hitoshi Mitake
2010-01-07 10:38 ` Hitoshi Mitake
2010-01-07 10:39 ` [PATCH 0/5] lockdep: Add information of file and line to lockdep_map Hitoshi Mitake
2010-01-13 9:52 ` Peter Zijlstra
2010-01-13 10:09 ` Ingo Molnar
2010-01-16 13:01 ` Hitoshi Mitake
2010-01-18 7:20 ` Peter Zijlstra [this message]
2010-01-26 5:56 ` [PATCH] Add type of locks to lock trace events Hitoshi Mitake
2010-01-28 10:21 ` Peter Zijlstra
2010-01-29 17:29 ` Frederic Weisbecker
2010-01-29 17:41 ` Peter Zijlstra
2010-01-29 22:12 ` Frederic Weisbecker
2010-02-24 9:02 ` [PATCH] Separate lock events with types Hitoshi Mitake
2010-03-26 23:33 ` Frederic Weisbecker
2010-04-05 10:37 ` Hitoshi Mitake
2010-04-06 8:26 ` Peter Zijlstra
2010-04-06 9:44 ` Frederic Weisbecker
2010-01-07 10:39 ` [PATCH 1/5] lockdep: Add file and line to initialize sequence of spin and rw lock Hitoshi Mitake
2010-01-07 10:39 ` [PATCH 2/5] lockdep: Add file and line to initialize sequence of rwsem Hitoshi Mitake
2010-01-07 10:39 ` [PATCH 3/5] " Hitoshi Mitake
2010-01-07 10:39 ` [PATCH 4/5] lockdep: Add file and line to initialize sequence of mutex Hitoshi Mitake
2010-01-07 10:39 ` [PATCH 5/5] lockdep: Fix the way to initialize class_mutex for information of file and line Hitoshi Mitake
2010-01-13 10:00 ` Ingo Molnar
2010-01-13 23:17 ` Greg KH
2010-01-13 23:19 ` Greg KH
2010-01-16 12:55 ` Hitoshi Mitake
2009-12-16 8:18 ` [tip:perf/lock] perf: Add util/include/linuxhash.h to include hash.h of kernel tip-bot for Hitoshi Mitake
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=1263799219.4283.0.camel@laptop \
--to=peterz@infradead.org \
--cc=fweisbec@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mitake@dcl.info.waseda.ac.jp \
--cc=paulus@samba.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