All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	mingo@elte.hu, linux-kernel@vger.kernel.org, h.mitake@gmail.com,
	Paul Mackerras <paulus@samba.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Jens Axboe <jens.axboe@oracle.com>,
	Jason Baron <jbaron@redhat.com>,
	Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Subject: Re: [PATCH] perf lock: Fix state machine to recognize lock sequence
Date: Wed, 21 Apr 2010 21:29:10 +0900	[thread overview]
Message-ID: <4BCEEF96.3060104@dcl.info.waseda.ac.jp> (raw)
In-Reply-To: <1271840158.1776.63.camel@laptop>

On 04/21/10 17:55, Peter Zijlstra wrote:
 > On Wed, 2010-04-21 at 03:26 +0200, Frederic Weisbecker wrote:
 >> The max lockdep depth may
 >> change in the future, or become variable, so we can't relay on that.
 >>
 > Change, possible, variable unlikely, you need a memory allocation to
 > extend it, and memory allocation takes locks, which is not a nice thing
 > to do in the middle of lockdep.

Thanks for your clear description.
It seems that we can think that maximum depth of lock will not be variable.

Thanks,
	Hitoshi

  reply	other threads:[~2010-04-21 12:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-10 10:44 Question about lock sequence Hitoshi Mitake
2010-04-10 13:07 ` Frederic Weisbecker
2010-04-10 15:12   ` Hitoshi Mitake
2010-04-16  8:44     ` [PATCH] perf lock: Fix state machine to recognize " Hitoshi Mitake
2010-04-21  1:26       ` Frederic Weisbecker
2010-04-21  8:55         ` Peter Zijlstra
2010-04-21 12:29           ` Hitoshi Mitake [this message]
2010-04-21 16:10           ` Frederic Weisbecker
2010-04-21  9:12         ` Hitoshi Mitake
2010-04-21 16:14           ` Frederic Weisbecker
2010-04-21 12:23         ` [PATCH v2] " Hitoshi Mitake
2010-04-22 22:54           ` Frederic Weisbecker
2010-04-27 12:55           ` [tip:perf/core] " tip-bot for Hitoshi Mitake
2010-04-10 14:01 ` Question about " Peter Zijlstra

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=4BCEEF96.3060104@dcl.info.waseda.ac.jp \
    --to=mitake@dcl.info.waseda.ac.jp \
    --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=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=xiaoguangrong@cn.fujitsu.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.