From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Steven Rostedt" <rostedt@goodmis.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>
Subject: Re: [GIT PULL] tracing/urgent for v2.6.31
Date: Thu, 11 Jun 2009 12:26:20 +0200 [thread overview]
Message-ID: <20090611102620.GB31719@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.01.0906102045420.6847@localhost.localdomain>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, 10 Jun 2009, Steven Rostedt wrote:
> >
> > Well it was:
> >
> > default y if DEBUG_KERNEL
> >
> > Where the rational was that if you want to debug the kernel, you
> > might want to see some tracing features that are available to
> > you.
>
> Sure. I think that FTRACE config is borderline fine, although I
> think tracing is pretty different from the debug options that
> don't need the user to actually do anything (like
> PAGEALLOC_DEBUG).
>
> It's the other ones I think were clearly dubious (ok, the MARKERS
> one isn't "clearly" dubious, since I have no idea why it got
> enabled, so I guess it would count as "unclearly dubious" then).
I agree that we have too many default-y options - we'll have a sweep
of all options and will default-disable the dubious (and unclearly
dubious) ones in a way that truly re-triggers user selection even if
the option is already enabled in the .config.
This particular new menu didnt actually change any of the existing
options or defaults: it just organized/grouped an already existing,
somewhat disorganized set of options and made it easier to disable
them summarily. Making _that_ default-n could have caused people to
accidentally disable a lot of options they had enabled in their
configs intentionally.
Ingo
prev parent reply other threads:[~2009-06-11 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 23:04 Ingo Molnar
2009-06-11 3:18 ` Linus Torvalds
2009-06-11 3:31 ` Steven Rostedt
2009-06-11 3:49 ` Linus Torvalds
2009-06-11 10:26 ` Ingo Molnar [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=20090611102620.GB31719@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®