From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Abhishek Sagar <sagar.abhishek@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
systemtap@sources.redhat.com
Subject: Re: instrumentation and kprobes really still "EXPERIMENTAL"?
Date: Mon, 2 Jul 2007 06:20:04 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707020619590.29879@localhost.localdomain> (raw)
In-Reply-To: <863e9df20707020256m75d24f52yfc5acd78cacffac7@mail.gmail.com>
On Mon, 2 Jul 2007, Abhishek Sagar wrote:
> On 7/2/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> > On Mon, 2 Jul 2007, Abhishek Sagar wrote:
> >
> > > On 7/1/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> > > > isn't kprobes mature enough to not be considered experimental anymore?
> > >
> > > That would vary from arch to arch.
> >
> > fair enough. however, at the very least, i'm thinking that the entire
> > "Instrumentation support" submenu can be made non-EXPERIMENTAL, while
> > individual entries therein can be EXPERIMENTAL on a choice-by-choice
> > basis or something like that.
>
> There's not a lot in that menu. It holds oprofile on every arch I
> grepped on. Oprofile might come across as being marked
> non-experimental but that may very well be due to the assumption
> that the menu that holds that option will enforce the EXPERIMENTAL
> check.
consider this random Kconfig file arch/x86_64/oprofile/Kconfig:
=============================
config PROFILING
bool "Profiling support (EXPERIMENTAL)"
help
Say Y here to enable the extended profiling support mechanisms used
by profilers such as OProfile.
config OPROFILE
tristate "OProfile system profiling (EXPERIMENTAL)"
depends on PROFILING
help
OProfile is a profiling system capable of profiling the
whole system, include the kernel, kernel modules, libraries,
and applications.
If unsure, say N.
==============================
the above is a bit silly. note that both prompts advertise
themselves as "EXPERIMENTAL" even though neither of them has such a
dependency. they *are*, however, part of an submenu that *is*
dependent on EXPERIMENTAL (although you'd never know that just by
looking at that Kconfig file). in short, it's just kind of ugly
hackery at the moment.
i made a suggestion a while back about having maturity levels like
"EXPERIMENTAL" **automatically** added to the displayed prompts when
you're doing a config -- that would go a long way to avoiding all this
manual adding of a maturity level to Kconfig prompts, but that's a
non-trivial change and is something the Kconfig folks would have to
handle.
my original point was simply that, based on its acceptance, it would
seem kprobes has progressed beyond the EXPERIMENTAL phase, that's all.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next prev parent reply other threads:[~2007-07-02 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 16:16 Robert P. J. Day
2007-07-02 8:54 ` Abhishek Sagar
2007-07-02 9:14 ` Robert P. J. Day
2007-07-02 9:56 ` Abhishek Sagar
2007-07-02 10:20 ` Robert P. J. Day [this message]
2007-07-02 11:48 ` Abhishek Sagar
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=Pine.LNX.4.64.0707020619590.29879@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sagar.abhishek@gmail.com \
--cc=systemtap@sources.redhat.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
all inboxes | Powered by JetHome®