public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Resurrect old pr_debug() semantics as pr_devel()
Date: Tue, 07 Apr 2009 12:08:47 +1000	[thread overview]
Message-ID: <1239070127.6565.9.camel@localhost> (raw)
In-Reply-To: <20090406212417.GC3212@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

On Mon, 2009-04-06 at 17:24 -0400, Jason Baron wrote:
> On Mon, Apr 06, 2009 at 02:30:03PM +1000, Michael Ellerman wrote:
> > pr_debug() used to produce zero code unless DEBUG was #defined. This is
> > now no longer the case in practice[1].
> > 
> > There are places where it's useful to have debugging printks, but we
> > don't want them to generate any code in production kernels.
> > 
> > So add a new macro, pr_devel(), for _devel_opment, to provide the old
> > semantics, ie. if the programmer doesn't explicitly enable debugging,
> > no code is produced.
> > 
> > [1]: You can turn CONFIG_DYNAMIC_DEBUG off, but it's enabled in at least
> >      one distro kernel, so it's not really a solution.
> > 
> 
> hmm...its designed to have low overhead when CONFIG_DYNAMIC_DEBUG
> is on, but none of the debugging printks are enabled. 

Sure, it does that fairly well, and there are places where it's a good
trade off to have the debug available at the cost of a bit more code.

> Is there a specific benchmark or test case that is unaccpetable?

Yes. Compiling with DYNAMIC_DEBUG=y generates a non-zero amount of code
for each pr_debug(), and in some places that is unacceptable.  :)

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      reply	other threads:[~2009-04-07  2:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06  4:30 [PATCH] Resurrect old pr_debug() semantics as pr_devel() Michael Ellerman
2009-04-06 21:24 ` Jason Baron
2009-04-07  2:08   ` Michael Ellerman [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=1239070127.6565.9.camel@localhost \
    --to=michael@ellerman.id.au \
    --cc=akpm@osdl.org \
    --cc=jbaron@redhat.com \
    --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