27 Oct, 2010
1 commit
-
op_name_from_perf_id() currently returns a local variable, which isn't
terribly productive. As we only handle a single PMU case for now, simply
allocate and free the string from the arch init/exit context and have
op_name_from_perf_id() hand back the cached string.This also takes UTS_MACHINE in to account, given that we build for
multiple architectures.Signed-off-by: Paul Mundt
11 Oct, 2010
1 commit
-
Now that we've got a generic perf-events based oprofile backend we might
as well make use of it seeing as SH doesn't do anything special with its
oprofile backend. Also introduce a new CONFIG_HW_PERF_EVENTS symbol so
that we can fallback to using the timer interrupt for oprofile if the
CPU doesn't support perf events.Also, to avoid a section mismatch warning we need to annotate
oprofile_arch_exit() with an __exit marker.Signed-off-by: Matt Fleming
Acked-by: Paul Mundt
Signed-off-by: Robert Richter
05 Nov, 2009
1 commit
-
This kills off the old SH7750 oprofile driver, preferring perf instead.
As this driver has a number of bugs that no one seems to have noticed,
it's safe to kill this off now rather than providing an extended
transition period.The old oprofile framework is still kept in place for now, primarily to
give out-of-tree drivers a chance to transition off. But this too will be
killed off in short order.Signed-off-by: Paul Mundt
22 Dec, 2008
2 commits
-
This re-implements the old op_model_null code in to something more
generic, where multiple drivers, backtrace, etc. can all be interfaced.
Based largely on arch/mips/oprofile/common.c.Signed-off-by: Paul Mundt
-
drivers/oprofile/ objects have proven to be problematic in this regard,
so simply disable -Werror for now.Signed-off-by: Paul Mundt
07 Nov, 2007
1 commit
-
Follow the MIPS and sparc64 changes for -Werror instrumentation.
Signed-off-by: Paul Mundt
27 Sep, 2006
1 commit
-
Update oprofile build rules for additional subtypes,
particularly SH7750S/SH7091.Signed-off-by: Paul Mundt
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!
