|author||Mike Frysinger <email@example.com>||2009-06-12 13:17:43 -0400|
|committer||Ingo Molnar <firstname.lastname@example.org>||2009-06-12 19:37:30 +0200|
perf_counter: Start documenting HAVE_PERF_COUNTERS requirements
Help out arch porters who want to support perf counters by listing some basic requirements. Signed-off-by: Mike Frysinger <email@example.com> Cc: Peter Zijlstra <firstname.lastname@example.org> Cc: Paul Mackerras <email@example.com> LKML-Reference: <firstname.lastname@example.org> Signed-off-by: Ingo Molnar <email@example.com>
Diffstat (limited to 'tools/perf/design.txt')
1 files changed, 15 insertions, 0 deletions
diff --git a/tools/perf/design.txt b/tools/perf/design.txt
index 860e116d979..f71e0d245cb 100644
@@ -440,3 +440,18 @@ by this process or by another, and doesn't affect any counters that
this process has created on other processes. It only enables or
disables the group leaders, not any other members in the groups.
+If your architecture does not have hardware performance metrics, you can
+still use the generic software counters based on hrtimers for sampling.
+So to start with, in order to add HAVE_PERF_COUNTERS to your Kconfig, you
+will need at least this:
+ - asm/perf_counter.h - a basic stub will suffice at first
+ - support for atomic64 types (and associated helper functions)
+ - set_perf_counter_pending() implemented
+If your architecture does have hardware capabilities, you can override the
+weak stub hw_perf_counter_init() to register hardware counters.