linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] perf-events: export enable/disable event symbols to kernel modules
Date: Wed, 10 Mar 2010 14:41:41 -0000	[thread overview]
Message-ID: <001301cac05f$cc85d730$65918590$@deacon@arm.com> (raw)
In-Reply-To: <1268231442.5279.1.camel@twins>

Hi Peter,

> Ah, very nice. Can something like that be done in general, like an
> arch-independent oprofile backend using perf, or is there too much
> arch-specific bits to the oprofile stuff?

In theory, it should be possible but it would require that:

(a) all the architectures that have OProfile support have equivalent support in Perf
(b) the OProfile userspace tools would need tweaking so that the kernel interface:
    i.)  is identical across different architectures
    ii.) has a 1:1 mapping with perf. That is, OProfile tools must agree with perf
         on things like number of counters and PMU name [which I don't think the
         generic perf code needs to care about].

> I know Robert talked about doing something like this, I just have no
> clue how arch specific this would be.

I think it would be a nightmare to fix up all the edge-cases that each architecture
has at the moment. If, in the long run, each architecture ends up defining their own
oprofile <-> perf interface then it would make sense to look at merging them at the
higher level.

Will

  reply	other threads:[~2010-03-10 14:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 10:41 [PATCH 0/6] ARM: oprofile: use perf-events framework as backend [v2] Will Deacon
2010-03-10 10:41 ` [PATCH 1/6] ARM: perf-events: add Realview PMU IRQs to pmu.c Will Deacon
2010-03-10 10:41   ` [PATCH 2/6] ARM: perf-events: use numeric ID to identify PMU Will Deacon
2010-03-10 10:41     ` [PATCH 3/6] ARM: perf-events: add support for xscale PMUs Will Deacon
2010-03-10 10:41       ` [PATCH 4/6] perf-events: export enable/disable event symbols to kernel modules Will Deacon
2010-03-10 10:41         ` [PATCH 5/6] ARM: oprofile: use perf-events framework as backend Will Deacon
2010-03-10 10:41           ` [PATCH 6/6] ARM: oprofile: remove old files and update KConfig Will Deacon
2010-03-10 10:56         ` [PATCH 4/6] perf-events: export enable/disable event symbols to kernel modules Peter Zijlstra
2010-03-10 11:47           ` Will Deacon
2010-03-10 14:30             ` Peter Zijlstra
2010-03-10 14:41               ` Will Deacon [this message]
2010-03-10 15:01               ` Robert Richter
2010-03-10 11:03     ` [PATCH 2/6] ARM: perf-events: use numeric ID to identify PMU Jamie Iles
2010-03-10 21:59   ` [PATCH 1/6] ARM: perf-events: add Realview PMU IRQs to pmu.c Tony Lindgren
2010-03-10 22:27     ` Albin Tonnerre
2010-03-10 22:34       ` Tony Lindgren
  -- strict thread matches above, loose matches on Subject: below --
2010-02-25 18:56 [PATCH 0/6] ARM: oprofile: use perf-events framework as backend Will Deacon
2010-02-25 18:56 ` [PATCH 1/6] ARM: perf-events: add Realview PMU IRQs to pmu.c Will Deacon
2010-02-25 18:56   ` [PATCH 2/6] ARM: perf-events: use numeric ID to identify PMU Will Deacon
2010-02-25 18:56     ` [PATCH 3/6] ARM: perf-events: add support for xscale PMUs Will Deacon
2010-02-25 18:56       ` [PATCH 4/6] perf-events: export enable/disable event symbols to kernel modules Will Deacon
2010-02-26  8:23         ` Ingo Molnar
2010-02-26  9:53           ` Will Deacon

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='001301cac05f$cc85d730$65918590$@deacon@arm.com' \
    --to=will.deacon@arm.com \
    --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).