From: Andrew Morton <akpm@osdl.org>
To: "Truong, Dan" <dan.truong@hp.com>
Cc: stephane.eranian@hp.com, perfmon@napali.hpl.hp.com,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
perfctr-devel@lists.sourceforge.net
Subject: Re: [perfmon] Re: quick overview of the perfmon2 interface
Date: Thu, 22 Dec 2005 13:46:44 +0000 [thread overview]
Message-ID: <20051222054644.0b9da029.akpm@osdl.org> (raw)
In-Reply-To: <3C87FFF91369A242B9C9147F8BD0908A02C69459@cacexc04.americas.cpqcorp.net>
"Truong, Dan" <dan.truong@hp.com> wrote:
>
> The PMU is becoming a standard commodity. Once Perfmon is
> "the" Linux interface, all the tools can align on it and
> coexist, push their R&D forward, and more importantly become
> fully productized for businesses usage.
>
The apparently-extreme flexibility of the perfmon interfaces would tend to
militate against that, actually. It'd become better productised if it had
one interface and stuck to it.
(I haven't processed Stephane's reply yet - will get there)
next prev parent reply other threads:[~2005-12-22 13:46 UTC|newest]
Thread overview: 19+ 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
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-20 18:37 Truong, Dan
2006-01-20 22:22 ` Andrew Morton
2006-01-25 20:33 ` Bryan O'Sullivan
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=20051222054644.0b9da029.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dan.truong@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 \
--cc=stephane.eranian@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