From: "ananth at in dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug kprobes/4748] Kprobes marked EXPERIMENTAL
Date: Mon, 09 Jul 2007 04:48:00 -0000 [thread overview]
Message-ID: <20070709044751.18504.qmail@sourceware.org> (raw)
In-Reply-To: <20070707003221.4748.jkenisto@us.ibm.com>
------- Additional Comments From ananth at in dot ibm dot com 2007-07-09 04:47 -------
Subject: Re: Kprobes marked EXPERIMENTAL
> i'm tempted to submit a patch that removes the top-level EXPERIMENTAL
> dependency from the Instrumentation menu in all those Kconfig files.
> if something is truly experimental, it makes more sense that it be
> tagged that way individually on a feature-by-feature basis.
>
> want me to do that as a starting point?
I agree that the tag needs to be granular. On the kprobes front, we need
to take a call on an arch basis. I'd say, based on testing over the past
couple of years, the EXPERIMENTAL tag can be removed from i386, x86_64,
powerpc and IA64.
Arch maintainers of sparc64, avr32 and s390 need to take a similar call.
Ananth
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4748
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-07-09 4:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 0:32 [Bug kprobes/4748] New: " jkenisto at us dot ibm dot com
2007-07-07 11:38 ` Robert P. J. Day
2007-07-07 11:38 ` [Bug kprobes/4748] " rpjday at mindspring dot com
2007-07-09 4:47 ` Ananth N Mavinakayanahalli
2007-07-09 4:48 ` ananth at in dot ibm dot com [this message]
2007-07-09 17:26 ` jkenisto at us dot ibm dot com
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=20070709044751.18504.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).