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 11:47:19 -0000 [thread overview]
Message-ID: <001201cac047$70b71c60$52255520$@deacon@arm.com> (raw)
In-Reply-To: <1268218566.8991.1.camel@twins>
Hello Peter,
> On Wed, 2010-03-10 at 10:41 +0000, Will Deacon wrote:
> > The perf_event_enable and perf_event_disable functions are used to
> > control the activation of perf-events for a given context or CPU.
> >
> > This patch exports these symbols so that they can be used by kernel
> > modules. Without these symbols, an event must be destroyed and recreated
> > to disable or enable it respectively. The maximum number of perf-events
> > is also made available to modules via the perf_get_max_events function.
>
> Where is the module that uses all this?
It's part of the same patchset:
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-March/011126.html
The idea is to use perf-events as the backend for OProfile to avoid replicating
the PMU accessor code.
Cheers,
Will
next prev parent reply other threads:[~2010-03-10 11:47 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 [this message]
2010-03-10 14:30 ` Peter Zijlstra
2010-03-10 14:41 ` Will Deacon
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='001201cac047$70b71c60$52255520$@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 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.