From: Andrew Morton <akpm@linux-foundation.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: eranian@gmail.com, "David Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch 00/24] perfmon3: introduction
Date: Wed, 22 Oct 2008 10:22:57 -0700 [thread overview]
Message-ID: <20081022102257.60dc8d08.akpm@linux-foundation.org> (raw)
In-Reply-To: <200810220958.23266.jbarnes@virtuousgeek.org>
On Wed, 22 Oct 2008 09:58:22 -0700 Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Wednesday, October 22, 2008 1:39 am stephane eranian wrote:
> > As you know, I have been involved with this project for quite some time
> > now. I have been through many ups and downs trying to get this merged
> > upstream. So rest assured of my full determination to bring this to the
> > point of success.
>
> I've been following this at a high level since using perfmon on ia64 several
> years ago. I have to say I'm impressed that you've put up with all the review
> and code churn (which to me often seemed arbitrary) without burning out.
>
> Honestly I think it sucks that perfmonN isn't upstream yet supporting all the
> various architectures you've been working with. You've obviously proven to be
> a much more responsive and end-user focused maintainer than several of the
> other fly by night profiling infrastructures we currently have in the kernel
> (the long abandoned oprofile and perfctr come to mind).
>
> As I mentioned at KS, I think it's about time we had a single point of contact
> for profiling in the kernel, to avoid the massive functional duplication we
> have today and make sure some kind of code sharing occurs; seems to me you'd
> be a good candidate for that sort of job.
>
> But regardless, I think it's about time this got merged. Linus? Andrew?
It is several years late. For me the problem has been that we do a lot
of review and have lots of discussion but then the trail goes cold for
six months and when it all pops up again the code has changed and/or
we've all forgotten about it again.
What it needs is a sustained effort to get it over the hump. How's
about getting it into linux-next asap and then we all agree to do the
re-re-re-review and runtime testing for a 2.6.29 merge?
next prev parent reply other threads:[~2008-10-22 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 15:05 eranian
2008-10-22 4:25 ` David Miller
2008-10-22 8:39 ` stephane eranian
2008-10-22 16:58 ` Jesse Barnes
2008-10-22 17:22 ` Andrew Morton [this message]
2008-10-23 7:19 ` stephane eranian
2008-11-10 2:41 ` Paul Mackerras
2008-11-10 15:24 ` stephane eranian
2008-11-11 0:29 ` stephane eranian
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=20081022102257.60dc8d08.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eranian@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome