public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Stephane Eranian <eranian@hpl.hp.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, perfmon@napali.hpl.hp.com,
	linux-ia64@vger.kernel.org, perfctr-devel@lists.sourceforge.net
Subject: Re: quick overview of the perfmon2 interface
Date: Thu, 22 Dec 2005 12:05:58 +0000	[thread overview]
Message-ID: <20051222120558.GA31303@infradead.org> (raw)
In-Reply-To: <20051222115632.GA8773@frankl.hpl.hp.com>

On Thu, Dec 22, 2005 at 03:56:32AM -0800, Stephane Eranian wrote:
> reason:
> 	- allow support of existing kernel profiling infratructures such as
> 	  Oprofile or VTUNE (the VTUNE driver is open-source)

last time I checked it was available in source, but not under an open-source
license.  has this changed?  In either case intel should contribute to the
kernel profiling infrastructure instead of doing their own thing.  Supporting
people to do their own private variant is always a bad thing.

> Let's take an example on Itanium. Take a user running a commercial distro
> based on 2.6. This user is given early access to a Montecito machine.

That scenario is totally uninteresting for kernel development.  we want
to encourage people to use upstream kernels, and not the bastardized vendor
crap.

I think you're adding totally pointless complexity everywhere for such
scenarious because HP apparently cares for such vendor mess.  Maybe you
should concentrate on what's best for upstream kernel development.  And
the most important thing is to reduce complexity by at least one magnitude.


  reply	other threads:[~2005-12-22 12:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19 11:31 quick overview of the perfmon2 interface Stephane Eranian
2005-12-20 10:51 ` Andrew Morton
2005-12-20 11:19   ` [Perfctr-devel] " Mikael Pettersson
2005-12-20 18:05   ` Tony Luck
2005-12-20 18:16     ` [Perfctr-devel] " Stephane Eranian
2005-12-20 23:52   ` David Gibson
2005-12-22 11:56   ` Stephane Eranian
2005-12-22 12:05     ` Christoph Hellwig [this message]
2005-12-22 15:37       ` [Perfctr-devel] " William Cohen
2005-12-22 17:23         ` Christoph Hellwig
2005-12-22 18:17           ` William Cohen
2005-12-22 18:36           ` John Reiser
2005-12-22 18:48   ` [perfmon] " Stephane Eranian
2005-12-21 22:39 ` Truong, Dan
2005-12-22 13:31 ` Truong, Dan
2005-12-22 13:46   ` Andrew Morton

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=20051222120558.GA31303@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@osdl.org \
    --cc=eranian@hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perfctr-devel@lists.sourceforge.net \
    --cc=perfmon@napali.hpl.hp.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