From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: instrumentation and kprobes really still "EXPERIMENTAL"?
Date: Sun, 1 Jul 2007 12:16:14 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707011204580.32355@localhost.localdomain> (raw)
i just noticed that, in the Kconfig files that support KPROBES, both
the "Instrumentation support" menu is still listed as EXPERIMENTAL,
while Kprobes support within is simultaneously dependent on that same
selection.
for one, that's kind of redundant and, for another, isn't kprobes
mature enough to not be considered experimental anymore? after all,
red hat is shipping fedora 7 with kprobes support on by default. that
kind of takes it out of the realm of experimental, doesn't it?
in addition, while most of the KPROBES config options depend on
KALLSYMS && EXPERIMENTAL && MODULES
the s390 architecture depends only on
EXPERIMENTAL && MODULES
and its instrumentation support is *not* listed as experimental.
also, the avr32 entry is in the file Kconfig.debug, and depends only
on DEBUG_KERNEL. just an observation.
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 reply other threads:[~2007-07-01 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 16:16 Robert P. J. Day [this message]
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
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.0707011204580.32355@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.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®