public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Anton Blanchard <anton@samba.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] improve spinlock debugging
Date: Thu, 20 Dec 2001 18:08:25 +0100	[thread overview]
Message-ID: <3C221B09.4090201@colorfullife.com> (raw)
In-Reply-To: <3C0BDC33.6E18C815@colorfullife.com> <20011219025332.GA18344@krispykreme>

Anton Blanchard wrote:

>
>What do you think of the idea below? We create arch specific spinlock
>functions as __foo and wrap the debugging bits around them as foo. This
>should also allow us to unify the UP and SMP spinlock debugging somewhat.
>
I tried to create a minimal patch, to reduce the probability of patch 
conflicts with earlier/future kernels.

I agree that your solutition is better if the patch is included in 
Linus/Marcelo's tree.
Have you asked Linus about it? I love runtime checks, but IIRC the 
majority of the kernel maintainers disagrees.

--
    Manfred


      parent reply	other threads:[~2001-12-20 17:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 20:10 [PATCH] improve spinlock debugging Manfred Spraul
2001-12-04  4:21 ` David S. Miller
2001-12-04  4:30   ` Robert Love
2001-12-04 20:30 ` george anzinger
2001-12-04 20:51   ` Robert Love
2001-12-04 21:25     ` george anzinger
2001-12-04 21:39       ` Robert Love
2001-12-04 22:06     ` Nigel Gamble
2001-12-04 22:23       ` Robert Love
2001-12-05  1:13         ` Roman Zippel
2001-12-05  7:41           ` george anzinger
2001-12-04 20:53   ` Manfred Spraul
2001-12-05  0:54     ` george anzinger
2001-12-04 21:20   ` Nigel Gamble
2001-12-04 21:27     ` george anzinger
2001-12-05  8:47 ` Giuliano Pochini
2001-12-05 15:42   ` Manfred Spraul
     [not found] ` <20011219025332.GA18344@krispykreme>
2001-12-20 17:08   ` Manfred Spraul [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=3C221B09.4090201@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.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