public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: David Rientjes <rientjes@google.com>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 2/2] lockdep: initialize lockdep debugging statistics
Date: Thu, 5 Mar 2009 12:05:22 +0100	[thread overview]
Message-ID: <20090305110522.GI32407@elte.hu> (raw)
In-Reply-To: <1236250159.4228.186.camel@laptop>


* Peter Zijlstra <peterz@infradead.org> wrote:

> On Thu, 2009-03-05 at 02:29 -0800, David Rientjes wrote:
> > The CONFIG_DEBUG_LOCKDEP statistics need to be initialized with
> > ATOMIC_INIT(0) since they are of type atomic_t.
> 
> And how does ATOMIC_INIT(0) differ from the global/static 
> storage being initialized to 0?
> 
> All I can see this doing it moving the variables from bss to 
> data for some compilers.

ok, i dropped it for now.

	Ingo

  reply	other threads:[~2009-03-05 11:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 10:29 [patch 1/2] lockdep: remove duplicate CONFIG_DEBUG_LOCKDEP definitions David Rientjes
2009-03-05 10:29 ` [patch 2/2] lockdep: initialize lockdep debugging statistics David Rientjes
2009-03-05 10:48   ` [tip:core/locking] " David Rientjes
2009-03-05 10:49   ` [patch 2/2] " Peter Zijlstra
2009-03-05 11:05     ` Ingo Molnar [this message]
2009-03-05 21:57       ` David Rientjes
2009-03-06  8:28         ` Peter Zijlstra
2009-03-06  9:56           ` David Rientjes
2009-03-06 10:19             ` Peter Zijlstra
2009-03-06 10:27               ` David Rientjes
2009-03-06 10:46                 ` Peter Zijlstra
2009-03-06 10:05           ` Li Zefan
2009-03-05 10:48 ` [tip:core/locking] lockdep: remove duplicate CONFIG_DEBUG_LOCKDEP definitions David Rientjes

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=20090305110522.GI32407@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rientjes@google.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