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 14:24:44 +0530 [thread overview]
Message-ID: <863e9df20707020154o5232e44ch37dd55811c377a8f@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707011204580.32355@localhost.localdomain>
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.
> 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.
This probably stems from the episodic growth kprobes across different
archs. It can be cleaned up I suppose.
--
Abhishek Sagar
P.S: Adding systemtap in CC.
-
> 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/
next prev parent reply other threads:[~2007-07-02 8:54 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 [this message]
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=863e9df20707020154o5232e44ch37dd55811c377a8f@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®