Re: [PATCH] Resurrect old pr_debug() semantics as pr_devel()

From: Jason Baron
Date: Mon Apr 06 2009 - 17:25:52 EST


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. Is there a
specific benchmark or test case that is unaccpetable?

thanks,

-Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/