From: "Abhishek Sagar" <sagar.abhishek@gmail.com>
To: "Robert P. J. Day" <rpjday@mindspring.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 17:18:11 +0530 [thread overview]
Message-ID: <863e9df20707020448o21c3baf2xda3528df312179c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707020619590.29879@localhost.localdomain>
On 7/2/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> 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.
Yes but pushing the EXPERIMENTAL check to individual menu members
shouldn't be done in a way which leads to an empty menu for any kernel
configuration. I suspect that this is why the EXPERIMENTAL check is on
the instrumentation menu in the first place.
> my original point was simply that, based on its acceptance, it would
> seem kprobes has progressed beyond the EXPERIMENTAL phase, that's all.
It's worth a look on some archs.
--
Abhishek Sagar
-
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2007-07-02 11:48 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
2007-07-02 11:48 ` Abhishek Sagar [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=863e9df20707020448o21c3baf2xda3528df312179c@mail.gmail.com \
--to=sagar.abhishek@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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®