11 Oct, 2010
1 commit
-
Move the perf-events backend from arch/arm/oprofile into
drivers/oprofile so that the code can be shared between architectures.This allows each architecture to maintain only a single copy of the PMU
accessor functions instead of one for both perf and OProfile. It also
becomes possible for other architectures to delete much of their
OProfile code in favour of the common code now available in
drivers/oprofile/oprofile_perf.c.Signed-off-by: Matt Fleming
Tested-by: Will Deacon
Signed-off-by: Robert Richter
17 May, 2010
1 commit
-
Enable hardware perf-events if CPU_HAS_PMU and select
HAVE_OPROFILE if HAVE_PERF_EVENTS. If no hardware support
is present, OProfile will fall back to timer mode.This patch also removes the old OProfile drivers in favour
of the code implemented by perf.Signed-off-by: Will Deacon
Signed-off-by: Russell King
01 Sep, 2008
1 commit
-
Add Oprofile kernel support for ARMv7.
Tested on OMAP3430 and OMAP3530 chipsets (Cortex-A8).Signed-off-by: Jean Pihet
Signed-off-by: Russell King
07 Feb, 2007
3 commits
-
Add the glue for ARM11 SMP oprofile support, which also supports the
performance monitor in the coherency unit.Signed-off-by: Russell King
-
Add oprofile glue for ARM11 (ARMv6) oprofile support. This
connects the ARM11 core profiling support to the oprofile code
for uniprocessor configurations.Signed-off-by: Russell King
-
Add basic support for the ARM11 profiling hardware. This is shared
between the ARM11 UP and ARM11 SMP oprofile support code.Signed-off-by: Russell King
28 Oct, 2005
1 commit
-
There is nothing special about having the init code separate from
the common code, so combine the two.Signed-off-by: Russell King
29 Jun, 2005
1 commit
-
Patch from Richard Purdie
Add functions to generate backtraces of both kernel and user processes
which allows oprofile's call graphing functionality to be used on arm.
This requires unstripped binaries/libs which use a frame pointer.Signed-off-by: Richard Purdie
Signed-off-by: Zwane Mwaikambo
Signed-off-by: Russell King
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!
