All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] Generalise ARM perf-events backend for oprofile
Date: Wed, 25 Aug 2010 09:19:01 +0000	[thread overview]
Message-ID: <1282727941.22370.606.camel@pasglop> (raw)
In-Reply-To: <1282727242.5727.7.camel@e102144-lin.cambridge.arm.com>

On Wed, 2010-08-25 at 10:07 +0100, Will Deacon wrote:
> Ideally, the OProfile userspace tools would talk native perf and we
> could do away with oprofilefs and the oprofile buffer altogether.
> Compatibility with the old [read current] OProfile tools can be
> maintained using these patches until the API is deprecated.
> 
> Or is that a bit too optimistic? :) 

Heh, well, dunno, I suspect just moving userspace to native perf tools
is going to happen as soon is not sooner :-)

Ben.


WARNING: multiple messages have this Message-ID (diff)
From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Generalise ARM perf-events backend for oprofile
Date: Wed, 25 Aug 2010 19:19:01 +1000	[thread overview]
Message-ID: <1282727941.22370.606.camel@pasglop> (raw)
In-Reply-To: <1282727242.5727.7.camel@e102144-lin.cambridge.arm.com>

On Wed, 2010-08-25 at 10:07 +0100, Will Deacon wrote:
> Ideally, the OProfile userspace tools would talk native perf and we
> could do away with oprofilefs and the oprofile buffer altogether.
> Compatibility with the old [read current] OProfile tools can be
> maintained using these patches until the API is deprecated.
> 
> Or is that a bit too optimistic? :) 

Heh, well, dunno, I suspect just moving userspace to native perf tools
is going to happen as soon is not sooner :-)

Ben.

WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Will Deacon <will.deacon@arm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Matt Fleming <matt@console-pimps.org>,
	linux-kernel@vger.kernel.org,
	Robert Richter <robert.richter@amd.com>,
	Paul Mundt <lethal@linux-sh.org>,
	Russell King <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org, linux-sh@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH 0/3] Generalise ARM perf-events backend for oprofile
Date: Wed, 25 Aug 2010 19:19:01 +1000	[thread overview]
Message-ID: <1282727941.22370.606.camel@pasglop> (raw)
In-Reply-To: <1282727242.5727.7.camel@e102144-lin.cambridge.arm.com>

On Wed, 2010-08-25 at 10:07 +0100, Will Deacon wrote:
> Ideally, the OProfile userspace tools would talk native perf and we
> could do away with oprofilefs and the oprofile buffer altogether.
> Compatibility with the old [read current] OProfile tools can be
> maintained using these patches until the API is deprecated.
> 
> Or is that a bit too optimistic? :) 

Heh, well, dunno, I suspect just moving userspace to native perf tools
is going to happen as soon is not sooner :-)

Ben.


  reply	other threads:[~2010-08-25  9:19 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23 10:46 [PATCH 0/3] Generalise ARM perf-events backend for oprofile Matt Fleming
2010-08-23 10:46 ` Matt Fleming
2010-08-23 10:46 ` Matt Fleming
2010-08-23 10:46 ` [PATCH 1/3] sh: Accessor functions for the sh_pmu state Matt Fleming
2010-08-23 10:46   ` Matt Fleming
2010-08-23 10:46   ` Matt Fleming
2010-08-23 10:46 ` [PATCH 2/3] oprofile: Abstract the perf-events backend Matt Fleming
2010-08-23 10:46   ` Matt Fleming
2010-08-23 10:46   ` Matt Fleming
2010-08-23 10:46 ` [PATCH 3/3] sh: Use the perf-events backend for oprofile Matt Fleming
2010-08-23 10:46   ` Matt Fleming
2010-08-23 10:46   ` Matt Fleming
2010-08-23 10:57 ` [PATCH 0/3] Generalise ARM " Christoph Hellwig
2010-08-23 10:57   ` Christoph Hellwig
2010-08-23 10:57   ` Christoph Hellwig
2010-08-23 11:17   ` Matt Fleming
2010-08-23 11:17     ` Matt Fleming
2010-08-23 11:17     ` Matt Fleming
2010-08-25  1:41   ` Benjamin Herrenschmidt
2010-08-25  1:41     ` Benjamin Herrenschmidt
2010-08-25  1:41     ` Benjamin Herrenschmidt
2010-08-25  9:07     ` Will Deacon
2010-08-25  9:07       ` Will Deacon
2010-08-25  9:07       ` Will Deacon
2010-08-25  9:19       ` Benjamin Herrenschmidt [this message]
2010-08-25  9:19         ` Benjamin Herrenschmidt
2010-08-25  9:19         ` Benjamin Herrenschmidt
2010-08-23 15:51 ` Will Deacon
2010-08-23 15:51   ` Will Deacon
2010-08-23 15:51   ` Will Deacon
2010-08-23 21:28   ` Matt Fleming
2010-08-23 21:28     ` Matt Fleming
2010-08-23 21:28     ` Matt Fleming

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=1282727941.22370.606.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linux-arm-kernel@lists.infradead.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.