linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lethal@linux-sh.org (Paul Mundt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/7] perf: New helper function for pmu name
Date: Thu, 7 Oct 2010 00:57:04 +0900	[thread overview]
Message-ID: <20101006155704.GB10220@linux-sh.org> (raw)
In-Reply-To: <20101006155026.GT13563@erda.amd.com>

On Wed, Oct 06, 2010 at 05:50:26PM +0200, Robert Richter wrote:
> On 06.10.10 09:30:41, Paul Mundt wrote:
> > On Wed, Oct 06, 2010 at 03:18:25PM +0200, Robert Richter wrote:
> > > So, I am also fine with implementing a generic perf_pmu_name() for sh
> > > and then derive the oprofile cpu_type string from it in the oprofile
> > > code.
> > > 
> > Again, this is unacceptable.
> 
> Paul,
> 
> maybe I misunderstood you, but isn't this you preferred solution? We
> make perf_pmu_name() part of the generic i/f and then derive the
> oprofile name from the pmu name provided by perf.
> 
Perhaps we've misunderstood each other. I thought what you meant is that
we would carry a special API deviation in the architecture code or expose
the sh_pmu structure to generic code, both of which I have no interest
in. My preferred solution is that we provide a perf_pmu_name() in the
generic perf code as a __weak and then override it in the sh code, where
we have sh_pmu visibility. This way we aren't providing any special APIs
and sh_pmu remains constrained to the sh perf events code.

  reply	other threads:[~2010-10-06 15:57 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 20:44 [PATCH V4 0/7] Generalise ARM perf-events backend for oprofile Matt Fleming
2010-10-04 20:44 ` [PATCH 1/7] perf: Add helper function to return number of counters Matt Fleming
2010-10-05  8:15   ` Paul Mundt
2010-10-06 12:14   ` Robert Richter
2010-10-06 12:35     ` Robert Richter
2010-10-06 13:41     ` Peter Zijlstra
2010-10-04 20:44 ` [PATCH 2/7] perf: New helper function for pmu name Matt Fleming
2010-10-05  8:10   ` Paul Mundt
2010-10-06 12:27   ` Robert Richter
2010-10-06 12:39     ` Paul Mundt
2010-10-06 13:18       ` Robert Richter
2010-10-06 13:30         ` Paul Mundt
2010-10-06 14:13           ` Paul Mundt
2010-10-06 15:37             ` Robert Richter
2010-10-06 15:46               ` Paul Mundt
2010-10-06 15:50           ` Robert Richter
2010-10-06 15:57             ` Paul Mundt [this message]
2010-10-06 18:15   ` Robert Richter
2010-10-06 18:38     ` Paul Mundt
2010-10-04 20:44 ` [PATCH 3/7] ARM: oprofile: Rename op_arm to oprofile_perf Matt Fleming
2010-10-06 12:41   ` Robert Richter
2010-10-04 20:44 ` [PATCH 4/7] ARM: oprofile: Move non-ARM code into separate init/exit Matt Fleming
2010-10-06 13:33   ` Robert Richter
2010-10-06 13:41     ` Paul Mundt
2010-10-06 14:49     ` Robert Richter
2010-10-06 14:53       ` Paul Mundt
2010-10-06 14:59         ` Robert Richter
2010-10-06 15:00           ` Paul Mundt
2010-10-06 18:23           ` Grant Likely
2010-10-06 18:44             ` Robert Richter
2010-10-06 18:50               ` Paul Mundt
2010-10-06 18:58               ` Grant Likely
2010-10-06 19:22                 ` Robert Richter
2010-10-04 20:44 ` [PATCH 5/7] oprofile: Abstract the perf-events backend Matt Fleming
2010-10-06 18:34   ` Robert Richter
2010-10-04 20:44 ` [PATCH 6/7] sh: oprofile: Use perf-events oprofile backend Matt Fleming
2010-10-05  8:08   ` Paul Mundt
2010-10-06 18:35   ` Robert Richter
2010-10-06 19:45     ` Matt Fleming
2010-10-06 21:03       ` Paul Mundt
2010-10-04 20:44 ` [PATCH 7/7] sh: Annotate oprofile_arch_exit() with __exit marker Matt Fleming
2010-10-05  8:16   ` Paul Mundt
2010-10-06 18:37   ` Robert Richter
  -- strict thread matches above, loose matches on Subject: below --
2010-10-09  0:46 [PATCH V5 0/7] Generalise ARM perf-events backend for oprofile Matt Fleming
2010-10-09  0:46 ` [PATCH 2/7] perf: New helper function for pmu name Matt Fleming
2010-10-11  9:18   ` Robert Richter
2010-10-11  9:31     ` Peter Zijlstra
2010-10-11 15:31   ` Paul Mundt

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=20101006155704.GB10220@linux-sh.org \
    --to=lethal@linux-sh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).