From: Frederic Weisbecker <fweisbec@gmail.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Adrian Bunk <bunk@stusta.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: Please revert "debug: Make CONFIG_EXPERT select CONFIG_DEBUG_KERNEL to unhide debug options"
Date: Fri, 30 Sep 2011 17:25:23 +0200 [thread overview]
Message-ID: <20110930152517.GE19053@somewhere> (raw)
In-Reply-To: <20110930150519.GA7980@leaf>
On Fri, Sep 30, 2011 at 08:05:19AM -0700, Josh Triplett wrote:
> On Fri, Sep 30, 2011 at 04:42:45PM +0300, Adrian Bunk wrote:
> > I was just wondering why I was asked about all the debug options when I
> > tried 3.1-rc8, and that was due to commit f505c553 (debug: Make
> > CONFIG_EXPERT select CONFIG_DEBUG_KERNEL to unhide debug options),
> > the full commit is below.
> >
> > It is wrong, and the author does not seem to understand how Kconfig works.
> >
> > The commit message is:
> >
> > Several debugging options currently default to y, such as
> > CONFIG_DEBUG_BUGVERBOSE and CONFIG_DEBUG_RODATA. Embedded users
> > might want to turn those options off to save space; however,
> > turning them off requires turning on CONFIG_DEBUG_KERNEL to
> > unhide them. Since CONFIG_DEBUG_KERNEL exists specifically to
> > unhide debugging options, and CONFIG_EXPERT exists specifically
> > to unhide options potentially needed by experts and/or embedded
> > users, make CONFIG_EXPERT automatically imply
> > CONFIG_DEBUG_KERNEL.
> >
> >
> > Let me point at the obvious fact that both CONFIG_DEBUG_BUGVERBOSE and
> > CONFIG_DEBUG_RODATA do depend on DEBUG_KERNEL, and are contrary to the
> > claim of the author of this patch never enabled with
> > CONFIG_DEBUG_KERNEL=n. [1]
>
> Not true:
>
> ~/src/linux-2.6$ rm .config
> ~/src/linux-2.6$ make allnoconfig
> HOSTCC scripts/basic/fixdep
> HOSTCC scripts/kconfig/conf.o
> HOSTCC scripts/kconfig/zconf.tab.o
> HOSTLD scripts/kconfig/conf
> scripts/kconfig/conf --allnoconfig Kconfig
> #
> # configuration written to .config
> #
> ~/src/linux-2.6$ grep BUGVERBOSE .config
> CONFIG_DEBUG_BUGVERBOSE=y
> ~/src/linux-2.6$ grep DEBUG_KERNEL .config
> # CONFIG_DEBUG_KERNEL is not set
>
> DEBUG_BUGVERBOSE does not depend on DEBUG_KERNEL; it just only shows up
> with DEBUG_KERNEL (and EXPERT) set. The *description* has a conditional
> on DEBUG_KERNEL and EXPERT:
>
> config DEBUG_BUGVERBOSE
> bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT
>
> That doesn't mean the same thing as "depends on DEBUG_KERNEL".
Indeed.
But for DEBUG_RODATA it is the case. That said given the issue described
with DEBUG_BUGVERSBOSE, it makes only the changelog buggy, not the patch.
Also the patch was supposed to have a broader cleanup effect:
https://lkml.org/lkml/2011/6/6/641
But we applied an earlier version by accident.
All in one I think we chose a wrong way to fix the issue. It's annoying to
have all the configs that are only visible with CONFIG_EXPERT spread all
around in random config menu.
Anything that has "if CONFIG_EXPERT" should probably be moved under the CONFIG_EXPERT
menu so that it's visible and found right away.
next prev parent reply other threads:[~2011-09-30 15:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 13:42 Please revert "debug: Make CONFIG_EXPERT select CONFIG_DEBUG_KERNEL to unhide debug options" Adrian Bunk
2011-09-30 15:05 ` Josh Triplett
2011-09-30 15:25 ` Frederic Weisbecker [this message]
2011-09-30 15:32 ` Frederic Weisbecker
2011-09-30 15:54 ` Adrian Bunk
2011-09-30 15:50 ` Adrian Bunk
2011-10-10 7:29 ` Ingo Molnar
2011-10-10 8:48 ` Adrian Bunk
2011-10-10 9:44 ` Mike Galbraith
2011-10-10 10:21 ` Ingo Molnar
2011-10-10 12:13 ` Adrian Bunk
2011-10-12 8:38 ` Ingo Molnar
2011-10-20 21:41 ` Adrian Bunk
2011-10-21 8:19 ` Michal Marek
2011-10-21 9:22 ` Adrian Bunk
2011-10-21 12:37 ` Michal Marek
2011-10-21 16:12 ` Adrian Bunk
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=20110930152517.GE19053@somewhere \
--to=fweisbec@gmail.com \
--cc=bunk@stusta.de \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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