From: Kyle McMartin <kyle@mcmartin.ca>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Al Viro <viro@ZenIV.linux.org.uk>, Ingo Molnar <mingo@elte.hu>,
"David S. Miller" <davem@davemloft.net>,
Stephane Eranian <eranian@googlemail.com>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] Performance Counters for Linux
Date: Fri, 12 Jun 2009 00:07:51 -0400 [thread overview]
Message-ID: <20090612040751.GA20922@bombadil.infradead.org> (raw)
In-Reply-To: <alpine.LFD.2.01.0906111005020.3573@localhost.localdomain>
[With my Fedora on.]
On Thu, Jun 11, 2009 at 10:06:55AM -0700, Linus Torvalds wrote:
>
>
> On Thu, 11 Jun 2009, Christoph Hellwig wrote:
> >
> > So what point is there in keeping it in-tree except making life hell for
> > packagers?
>
> Give it up. Packagers can trivially generate their own sub-packages. They
> do it all the time. They already do it for the user-mode header files,
> extracted from the kernel - something you've worked on yourself.
>
> So your point is clearly bogus, and dishonest.
>
> You haven't actually looked the real problem in the eye, and acknowledged
> the disaster that is oprofile. Let's give a _new_ approach a chance, and
> see if we can avoid the mistakes of yesteryear this time.
>
This is actually somewhat complicated for (at least, I can only speak
from experience for...) Fedora and Debian/Ubuntu. Having this in-kernel
means any bugfixes needed for the 'perf' tool, require patching the
kernel source, which will result in a whole new kernel rpm being built.
So in order to update their 'perf' tool, users will get a new kernel,
debuginfo, etc., with it.
So either we need to split it out into its own source tarball, or ship
the kernel source again in a seperate source package. I know which I'm
going to tend to favour...
Obviously, I understand the reasons for doing this, but I don't really
see it as a sensible long term option for a mature tool. But,
whatever, it's not my call. We'll just work around whatever happens.
regards, Kyle
next prev parent reply other threads:[~2009-06-12 4:08 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 16:03 Ingo Molnar
2009-06-11 16:17 ` Christoph Hellwig
2009-06-11 16:26 ` Linus Torvalds
2009-06-11 16:34 ` Marcel Holtmann
2009-06-11 16:38 ` Linus Torvalds
2009-06-11 16:46 ` Christoph Hellwig
2009-06-11 16:54 ` Linus Torvalds
2009-06-11 16:47 ` Marcel Holtmann
2009-06-11 18:04 ` David Newall
2009-06-11 16:52 ` Al Viro
2009-06-11 16:56 ` Peter Zijlstra
2009-06-11 17:00 ` Christoph Hellwig
2009-06-11 17:05 ` Ray Lee
2009-06-11 17:08 ` Marcel Holtmann
2009-06-11 17:12 ` Al Viro
2009-06-11 17:22 ` Ray Lee
2009-06-11 17:06 ` Linus Torvalds
2009-06-11 17:59 ` Pekka Enberg
2009-06-11 18:10 ` David Newall
2009-06-11 18:21 ` Linus Torvalds
2009-06-11 18:38 ` David Newall
2009-06-11 18:44 ` Linus Torvalds
2009-06-11 19:07 ` David Newall
2009-06-11 19:23 ` Linus Torvalds
2009-06-11 19:29 ` Linus Torvalds
2009-06-11 19:35 ` David Newall
2009-06-11 19:49 ` Linus Torvalds
2009-06-12 1:43 ` Robert Richter
2009-06-12 3:21 ` David Newall
2009-06-11 19:37 ` David Newall
2009-06-11 18:51 ` Christoph Hellwig
2009-06-11 19:05 ` Marcel Holtmann
2009-06-11 18:24 ` Martin Bligh
2009-06-11 18:34 ` Linus Torvalds
2009-06-11 20:23 ` Ingo Molnar
2009-06-11 20:49 ` Marcel Holtmann
2009-06-11 21:08 ` Sam Ravnborg
2009-06-11 21:17 ` Marcel Holtmann
2009-06-11 21:26 ` Sam Ravnborg
2009-06-11 22:18 ` Jiri Slaby
2009-06-11 22:27 ` Linus Torvalds
2009-06-11 22:38 ` Alan Cox
2009-06-11 22:49 ` Linus Torvalds
2009-06-12 7:35 ` Alan Cox
2009-06-11 23:19 ` Al Viro
2009-06-11 23:25 ` Linus Torvalds
2009-06-12 0:26 ` Al Viro
2009-06-12 2:58 ` Linus Torvalds
2009-06-12 4:05 ` Al Viro
2009-06-11 21:59 ` Steven Rostedt
2009-06-12 10:19 ` Jörn Engel
2009-06-11 21:14 ` Ingo Molnar
2009-06-28 1:19 ` Felipe Contreras
2009-06-11 19:58 ` Andrew Morton
2009-06-11 20:09 ` Linus Torvalds
2009-06-12 4:07 ` Kyle McMartin [this message]
2009-06-11 16:58 ` Linus Torvalds
2009-06-11 18:50 ` Sam Ravnborg
2009-06-15 13:41 ` Giacomo A. Catenazzi
2009-06-15 15:18 ` Sam Ravnborg
2009-06-12 9:56 ` stephane eranian
2009-06-12 10:28 ` Ingo Molnar
2009-06-18 21:58 ` stephane eranian
2009-06-22 13:10 ` Performance analysis under Linux (was: Re: [GIT PULL] Performance Counters for Linux) Ingo Molnar
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=20090612040751.GA20922@bombadil.infradead.org \
--to=kyle@mcmartin.ca \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eranian@googlemail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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®