From: Dave Jones <davej@redhat.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
levon@movementarian.org, phil.el@wanadoo.fr,
Andrew Morton <akpm@osdl.org>
Subject: Re: Is OPROFILE actively maintained?
Date: Sun, 21 May 2006 15:57:10 -0400 [thread overview]
Message-ID: <20060521195710.GL8250@redhat.com> (raw)
In-Reply-To: <20060521194915.GA2153@taniwha.stupidest.org>
On Sun, May 21, 2006 at 12:49:15PM -0700, Chris Wedgwood wrote:
> On Fri, May 19, 2006 at 07:53:22PM -0700, Chris Wedgwood wrote:
>
> > oprofile isn't new and a lot of developers use it. Drop the
> > EXPERIMENTAL.
>
> Some feedback claims this is not the case and that "it's unmaintained,
> rarely well-tested, and may still need changes for some forthcoming
> JVM stuff. and the tools aren't yet at 1.0".
>
> Given that it should probably stay EXPERIMENTAL for now. I wonder if
> left unmaintained for much longer if it should be potentially marked
> BROKEN and/or scheduled for removal?
Why on earth would we want to remove a working feature ?
Just because it isn't getting patched every release doesn't mean
it's rotting, Oprofile is actually one of the few kernel features which I
don't recall a single regression in since 2.6.0
BROKEN is for stuff that doesn't compile, or is fundamentally flawed
beyond repair at the current time (For example, needs infrastructure
work to happen before it can work correctly).
Oprofile fits neither of those categories.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-05-21 19:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 2:53 [PATCH] i386 Don't conside oprofile EXPERIMENTAL anymore Chris Wedgwood
2006-05-21 19:49 ` Is OPROFILE actively maintained? Chris Wedgwood
2006-05-21 19:57 ` Dave Jones [this message]
2006-05-21 20:17 ` Chris Wedgwood
2006-05-21 20:49 ` Dave Jones
2006-05-21 20:56 ` Chris Wedgwood
2006-05-21 20:25 ` John Levon
2006-05-22 11:51 ` Alan Cox
2006-05-22 15:15 ` John Levon
2006-05-22 17:50 ` Måns Rullgård
2006-05-22 18:13 ` Chris Wedgwood
2006-05-22 15:27 ` Chris Wedgwood
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=20060521195710.GL8250@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=cw@f00f.org \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phil.el@wanadoo.fr \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.