public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Huey (hui) <billh@gnuppy.monkey.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Chen, Tim C" <tim.c.chen@intel.com>,
	linux-kernel@vger.kernel.org, "Siddha,
	Suresh B" <suresh.b.siddha@intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Bill Huey (hui)" <billh@gnuppy.monkey.org>,
	Daniel Walker <dwalker@mvista.com>
Subject: [PATCH] lock stat for -rt 2.6.20-rc2-rt2.2.lock_stat.patch
Date: Tue, 2 Jan 2007 23:41:24 -0800	[thread overview]
Message-ID: <20070103074124.GA25594@gnuppy.monkey.org> (raw)
In-Reply-To: <20061230111940.GA8412@elte.hu>

On Sat, Dec 30, 2006 at 12:19:40PM +0100, Ingo Molnar wrote:
> your patch looks pretty ok to me in principle. A couple of suggestions 
> to make it more mergable:
> 
>  - instead of BUG_ON()s please use DEBUG_LOCKS_WARN_ON() and make sure 
>    the code is never entered again if one assertion has been triggered.
>    Pass down a return result of '0' to signal failure. See
>    kernel/lockdep.c about how to do this. One thing we dont need are
>    bugs in instrumentation bringing down a machine.

I'm using a non-fatal error checking instead of BUG_ON. BUG_ON was a more
aggressive way that I use to find problem initiallly.

>  - remove dead (#if 0) code

Done.

>  - Documentation/CodingStyle compliance - the code is not ugly per se
>    but still looks a bit 'alien' - please try to make it look Linuxish,
>    if i apply this we'll probably stick with it forever. This is the
>    major reason i havent applied it yet.

I reformatted most of the patch to be 80 column limited. I simplified a
number of names, but I'm open to suggestions and patches to how to go
about this. Much of this code was a style experiment, but now I have to
make this more mergable.

>  - the xfs/wrap_lock change looks bogus - the lock is initialized
>    already. What am i missing?

Correct. This has been removed.

I've applied Daniel Walker's changes as well.

Patch here:

	http://mmlinux.sourceforge.net/public/patch-2.6.20-rc2-rt2.2.lock_stat.patch

bill


  parent reply	other threads:[~2007-01-03  7:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-27  0:51 2.6.19-rt14 slowdown compared to 2.6.19 Chen, Tim C
2006-12-29 23:26 ` [PATCH] lock stat for -rt 2.6.20-rc2-rt2 [was Re: 2.6.19-rt14 slowdown compared to 2.6.19] Bill Huey
2006-12-30 11:19   ` Ingo Molnar
2006-12-30 14:56     ` Daniel Walker
2006-12-30 19:32       ` Bill Huey
2007-01-03  7:41     ` Bill Huey [this message]
2007-01-03 23:59       ` [PATCH] lock stat for -rt 2.6.20-rc2-rt2.2.lock_stat.patch Chen, Tim C
2007-01-04  0:12         ` Bill Huey
2007-01-04  0:25           ` Chen, Tim C
2007-01-04  0:29             ` Bill Huey
2007-01-04  0:46               ` Chen, Tim C
2007-01-04  1:00                 ` Bill Huey
2007-01-04  1:07                   ` Bill Huey
2007-01-04  1:11                   ` Chen, Tim C
2007-01-04  1:27                     ` Bill Huey
2007-01-04  2:14                       ` Chen, Tim C
2007-01-04  8:12                         ` Bill Huey
2007-01-04  4:46       ` Ingo Molnar
2007-01-24 23:06         ` Bill Huey
2007-01-25  8:39           ` Ingo Molnar
2007-01-24 11:31       ` Ingo Molnar
2007-01-24 22:52         ` Bill Huey
2007-01-02 22:51   ` [PATCH] lock stat for -rt 2.6.20-rc2-rt2 [was Re: 2.6.19-rt14 slowdown compared to 2.6.19] Chen, Tim C
2007-01-02 23:12     ` Bill Huey
2007-01-02 23:47       ` Bill Huey

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=20070103074124.GA25594@gnuppy.monkey.org \
    --to=billh@gnuppy.monkey.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox