perf: Do the big rename: Performance Counters -> Performance Events
Bye-bye Performance Counters, welcome Performance Events!
In the past few months the perfcounters subsystem has grown out its
initial role of counting hardware events, and has become (and is
becoming) a much broader generic event enumeration, reporting, logging,
monitoring, analysis facility.
Naming its core object 'perf_counter' and naming the subsystem
'perfcounters' has become more and more of a misnomer. With pending
code like hw-breakpoints support the 'counter' name is less and
less appropriate.
All in one, we've decided to rename the subsystem to 'performance
events' and to propagate this rename through all fields, variables
and API names. (in an ABI compatible fashion)
The word 'event' is also a bit shorter than 'counter' - which makes
it slightly more convenient to write/handle as well.
Thanks goes to Stephane Eranian who first observed this misnomer and
suggested a rename.
User-space tooling and ABI compatibility is not affected - this patch
should be function-invariant. (Also, defconfigs were not touched to
keep the size down.)
This patch has been generated via the following script:
FILES=$(find * -type f | grep -vE 'oprofile|[^K]config')
sed -i \
-e 's/PERF_EVENT_/PERF_RECORD_/g' \
-e 's/PERF_COUNTER/PERF_EVENT/g' \
-e 's/perf_counter/perf_event/g' \
-e 's/nb_counters/nb_events/g' \
-e 's/swcounter/swevent/g' \
-e 's/tpcounter_event/tp_event/g' \
$FILES
for N in $(find . -name perf_counter.[ch]); do
M=$(echo $N | sed 's/perf_counter/perf_event/g')
mv $N $M
done
FILES=$(find . -name perf_event.*)
sed -i \
-e 's/COUNTER_MASK/REG_MASK/g' \
-e 's/COUNTER/EVENT/g' \
-e 's/\<event\>/event_id/g' \
-e 's/counter/event/g' \
-e 's/Counter/Event/g' \
$FILES
... to keep it as correct as possible. This script can also be
used by anyone who has pending perfcounters patches - it converts
a Linux kernel tree over to the new naming. We tried to time this
change to the point in time where the amount of pending patches
is the smallest: the end of the merge window.
Namespace clashes were fixed up in a preparatory patch - and some
stylistic fallout will be fixed up in a subsequent patch.
( NOTE: 'counters' are still the proper terminology when we deal
with hardware registers - and these sed scripts are a bit
over-eager in renaming them. I've undone some of that, but
in case there's something left where 'counter' would be
better than 'event' we can undo that on an individual basis
instead of touching an otherwise nicely automated patch. )
Suggested-by: Stephane Eranian <eranian@google.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Acked-by: Paul Mackerras <paulus@samba.org>
Reviewed-by: Arjan van de Ven <arjan@linux.intel.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Howells <dhowells@redhat.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: <linux-arch@vger.kernel.org>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-09-21 03:02:48 -07:00
|
|
|
#ifndef __PERF_RECORD_H
|
|
|
|
#define __PERF_RECORD_H
|
2009-09-24 09:02:18 -07:00
|
|
|
|
2009-12-27 16:37:00 -07:00
|
|
|
#include <limits.h>
|
|
|
|
|
2009-08-12 01:19:53 -07:00
|
|
|
#include "../perf.h"
|
2009-12-27 16:37:00 -07:00
|
|
|
#include "map.h"
|
2009-08-12 01:19:53 -07:00
|
|
|
|
2009-08-13 02:47:55 -07:00
|
|
|
/*
|
|
|
|
* PERF_SAMPLE_IP | PERF_SAMPLE_TID | *
|
|
|
|
*/
|
2009-08-12 01:19:53 -07:00
|
|
|
struct ip_event {
|
|
|
|
struct perf_event_header header;
|
|
|
|
u64 ip;
|
|
|
|
u32 pid, tid;
|
|
|
|
unsigned char __more_data[];
|
|
|
|
};
|
|
|
|
|
|
|
|
struct mmap_event {
|
|
|
|
struct perf_event_header header;
|
|
|
|
u32 pid, tid;
|
|
|
|
u64 start;
|
|
|
|
u64 len;
|
|
|
|
u64 pgoff;
|
|
|
|
char filename[PATH_MAX];
|
|
|
|
};
|
|
|
|
|
|
|
|
struct comm_event {
|
|
|
|
struct perf_event_header header;
|
|
|
|
u32 pid, tid;
|
|
|
|
char comm[16];
|
|
|
|
};
|
|
|
|
|
|
|
|
struct fork_event {
|
|
|
|
struct perf_event_header header;
|
|
|
|
u32 pid, ppid;
|
|
|
|
u32 tid, ptid;
|
2009-09-11 22:52:47 -07:00
|
|
|
u64 time;
|
2009-08-12 01:19:53 -07:00
|
|
|
};
|
|
|
|
|
|
|
|
struct lost_event {
|
|
|
|
struct perf_event_header header;
|
|
|
|
u64 id;
|
|
|
|
u64 lost;
|
|
|
|
};
|
|
|
|
|
2009-08-13 02:47:55 -07:00
|
|
|
/*
|
|
|
|
* PERF_FORMAT_ENABLED | PERF_FORMAT_RUNNING | PERF_FORMAT_ID
|
|
|
|
*/
|
2009-08-12 01:19:53 -07:00
|
|
|
struct read_event {
|
|
|
|
struct perf_event_header header;
|
2009-09-16 04:45:00 -07:00
|
|
|
u32 pid, tid;
|
2009-08-12 01:19:53 -07:00
|
|
|
u64 value;
|
|
|
|
u64 time_enabled;
|
|
|
|
u64 time_running;
|
|
|
|
u64 id;
|
|
|
|
};
|
|
|
|
|
2009-12-06 04:08:24 -07:00
|
|
|
struct sample_event {
|
2009-09-11 22:53:00 -07:00
|
|
|
struct perf_event_header header;
|
|
|
|
u64 array[];
|
|
|
|
};
|
|
|
|
|
2009-12-06 04:08:24 -07:00
|
|
|
struct sample_data {
|
|
|
|
u64 ip;
|
|
|
|
u32 pid, tid;
|
|
|
|
u64 time;
|
|
|
|
u64 addr;
|
|
|
|
u64 id;
|
|
|
|
u64 stream_id;
|
|
|
|
u64 period;
|
perf tools: Reorganize some structs to save space
Using 'pahole --packable' I found some structs that could be reorganized
to eliminate alignment holes, in some cases getting them to be cacheline
multiples.
[acme@doppio linux-2.6-tip]$ codiff perf.old ~/bin/perf
builtin-annotate.c:
struct perf_session | -8
struct perf_header | -8
2 structs changed
builtin-diff.c:
struct sample_data | -8
1 struct changed
diff__process_sample_event | -8
1 function changed, 8 bytes removed, diff: -8
builtin-sched.c:
struct sched_atom | -8
1 struct changed
builtin-timechart.c:
struct per_pid | -8
1 struct changed
cmd_timechart | -16
1 function changed, 16 bytes removed, diff: -16
builtin-probe.c:
struct perf_probe_point | -8
struct perf_probe_event | -8
2 structs changed
opt_add_probe_event | -3
1 function changed, 3 bytes removed, diff: -3
util/probe-finder.c:
struct probe_finder | -8
1 struct changed
find_kprobe_trace_events | -16
1 function changed, 16 bytes removed, diff: -16
/home/acme/bin/perf:
4 functions changed, 43 bytes removed, diff: -43
[acme@doppio linux-2.6-tip]$
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-04-05 08:53:45 -07:00
|
|
|
u32 cpu;
|
2009-12-06 04:08:24 -07:00
|
|
|
u32 raw_size;
|
|
|
|
void *raw_data;
|
perf tools: Reorganize some structs to save space
Using 'pahole --packable' I found some structs that could be reorganized
to eliminate alignment holes, in some cases getting them to be cacheline
multiples.
[acme@doppio linux-2.6-tip]$ codiff perf.old ~/bin/perf
builtin-annotate.c:
struct perf_session | -8
struct perf_header | -8
2 structs changed
builtin-diff.c:
struct sample_data | -8
1 struct changed
diff__process_sample_event | -8
1 function changed, 8 bytes removed, diff: -8
builtin-sched.c:
struct sched_atom | -8
1 struct changed
builtin-timechart.c:
struct per_pid | -8
1 struct changed
cmd_timechart | -16
1 function changed, 16 bytes removed, diff: -16
builtin-probe.c:
struct perf_probe_point | -8
struct perf_probe_event | -8
2 structs changed
opt_add_probe_event | -3
1 function changed, 3 bytes removed, diff: -3
util/probe-finder.c:
struct probe_finder | -8
1 struct changed
find_kprobe_trace_events | -16
1 function changed, 16 bytes removed, diff: -16
/home/acme/bin/perf:
4 functions changed, 43 bytes removed, diff: -43
[acme@doppio linux-2.6-tip]$
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>
LKML-Reference: <new-submission>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2010-04-05 08:53:45 -07:00
|
|
|
struct ip_callchain *callchain;
|
2009-12-06 04:08:24 -07:00
|
|
|
};
|
|
|
|
|
perf symbols: Use the buildids if present
With this change 'perf record' will intercept PERF_RECORD_MMAP
calls, creating a linked list of DSOs, then when the session
finishes, it will traverse this list and read the buildids,
stashing them at the end of the file and will set up a new
feature bit in the header bitmask.
'perf report' will then notice this feature and populate the
'dsos' list and set the build ids.
When reading the symtabs it will refuse to load from a file that
doesn't have the same build id. This improves the
reliability of the profiler output, as symbols and profiling
data is more guaranteed to match.
Example:
[root@doppio ~]# perf report | head
/home/acme/bin/perf with build id b1ea544ac3746e7538972548a09aadecc5753868 not found, continuing without symbols
# Samples: 2621434559
#
# Overhead Command Shared Object Symbol
# ........ ............... ............................. ......
#
7.91% init [kernel] [k] read_hpet
7.64% init [kernel] [k] mwait_idle_with_hints
7.60% swapper [kernel] [k] read_hpet
7.60% swapper [kernel] [k] mwait_idle_with_hints
3.65% init [kernel] [k] 0xffffffffa02339d9
[root@doppio ~]#
In this case the 'perf' binary was an older one, vanished,
so its symbols probably wouldn't match or would cause subtly
different (and misleading) output.
Next patches will support the kernel as well, reading the build
id notes for it and the modules from /sys.
Another patch should also introduce a new plumbing command:
'perf list-buildids'
that will then be used in porcelain that is distro specific to
fetch -debuginfo packages where such buildids are present. This
will in turn allow for one to run 'perf record' in one machine
and 'perf report' in another.
Future work on having the buildid sent directly from the kernel
in the PERF_RECORD_MMAP event is needed to close races, as the
DSO can be changed during a 'perf record' session, but this
patch at least helps with non-corner cases and current/older
kernels.
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Frank Ch. Eigler <fche@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Jason Baron <jbaron@redhat.com>
Cc: Jim Keniston <jkenisto@us.ibm.com>
Cc: K. Prasad <prasad@linux.vnet.ibm.com>
Cc: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Roland McGrath <roland@redhat.com>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
LKML-Reference: <1257367843-26224-1-git-send-email-acme@infradead.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-11-04 13:50:43 -07:00
|
|
|
#define BUILD_ID_SIZE 20
|
|
|
|
|
|
|
|
struct build_id_event {
|
|
|
|
struct perf_event_header header;
|
2010-04-18 22:32:50 -07:00
|
|
|
pid_t pid;
|
perf symbols: Use the buildids if present
With this change 'perf record' will intercept PERF_RECORD_MMAP
calls, creating a linked list of DSOs, then when the session
finishes, it will traverse this list and read the buildids,
stashing them at the end of the file and will set up a new
feature bit in the header bitmask.
'perf report' will then notice this feature and populate the
'dsos' list and set the build ids.
When reading the symtabs it will refuse to load from a file that
doesn't have the same build id. This improves the
reliability of the profiler output, as symbols and profiling
data is more guaranteed to match.
Example:
[root@doppio ~]# perf report | head
/home/acme/bin/perf with build id b1ea544ac3746e7538972548a09aadecc5753868 not found, continuing without symbols
# Samples: 2621434559
#
# Overhead Command Shared Object Symbol
# ........ ............... ............................. ......
#
7.91% init [kernel] [k] read_hpet
7.64% init [kernel] [k] mwait_idle_with_hints
7.60% swapper [kernel] [k] read_hpet
7.60% swapper [kernel] [k] mwait_idle_with_hints
3.65% init [kernel] [k] 0xffffffffa02339d9
[root@doppio ~]#
In this case the 'perf' binary was an older one, vanished,
so its symbols probably wouldn't match or would cause subtly
different (and misleading) output.
Next patches will support the kernel as well, reading the build
id notes for it and the modules from /sys.
Another patch should also introduce a new plumbing command:
'perf list-buildids'
that will then be used in porcelain that is distro specific to
fetch -debuginfo packages where such buildids are present. This
will in turn allow for one to run 'perf record' in one machine
and 'perf report' in another.
Future work on having the buildid sent directly from the kernel
in the PERF_RECORD_MMAP event is needed to close races, as the
DSO can be changed during a 'perf record' session, but this
patch at least helps with non-corner cases and current/older
kernels.
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Frank Ch. Eigler <fche@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Jason Baron <jbaron@redhat.com>
Cc: Jim Keniston <jkenisto@us.ibm.com>
Cc: K. Prasad <prasad@linux.vnet.ibm.com>
Cc: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Roland McGrath <roland@redhat.com>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
LKML-Reference: <1257367843-26224-1-git-send-email-acme@infradead.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-11-04 13:50:43 -07:00
|
|
|
u8 build_id[ALIGN(BUILD_ID_SIZE, sizeof(u64))];
|
|
|
|
char filename[];
|
|
|
|
};
|
2009-09-11 22:53:00 -07:00
|
|
|
|
2010-05-02 13:05:29 -07:00
|
|
|
enum perf_user_event_type { /* above any possible kernel type */
|
2010-04-01 21:59:19 -07:00
|
|
|
PERF_RECORD_HEADER_ATTR = 64,
|
2010-04-01 21:59:20 -07:00
|
|
|
PERF_RECORD_HEADER_EVENT_TYPE = 65,
|
2010-04-01 21:59:21 -07:00
|
|
|
PERF_RECORD_HEADER_TRACING_DATA = 66,
|
2010-04-01 21:59:22 -07:00
|
|
|
PERF_RECORD_HEADER_BUILD_ID = 67,
|
2010-05-02 13:05:29 -07:00
|
|
|
PERF_RECORD_FINISHED_ROUND = 68,
|
2010-04-01 21:59:19 -07:00
|
|
|
PERF_RECORD_HEADER_MAX
|
|
|
|
};
|
|
|
|
|
|
|
|
struct attr_event {
|
|
|
|
struct perf_event_header header;
|
|
|
|
struct perf_event_attr attr;
|
|
|
|
u64 id[];
|
2010-04-01 21:59:15 -07:00
|
|
|
};
|
|
|
|
|
2010-04-01 21:59:20 -07:00
|
|
|
#define MAX_EVENT_NAME 64
|
|
|
|
|
|
|
|
struct perf_trace_event_type {
|
|
|
|
u64 event_id;
|
|
|
|
char name[MAX_EVENT_NAME];
|
|
|
|
};
|
|
|
|
|
|
|
|
struct event_type_event {
|
|
|
|
struct perf_event_header header;
|
|
|
|
struct perf_trace_event_type event_type;
|
|
|
|
};
|
|
|
|
|
2010-04-01 21:59:21 -07:00
|
|
|
struct tracing_data_event {
|
|
|
|
struct perf_event_header header;
|
|
|
|
u32 size;
|
|
|
|
};
|
|
|
|
|
2009-08-12 01:19:53 -07:00
|
|
|
typedef union event_union {
|
|
|
|
struct perf_event_header header;
|
|
|
|
struct ip_event ip;
|
|
|
|
struct mmap_event mmap;
|
|
|
|
struct comm_event comm;
|
|
|
|
struct fork_event fork;
|
|
|
|
struct lost_event lost;
|
|
|
|
struct read_event read;
|
2009-09-11 22:53:00 -07:00
|
|
|
struct sample_event sample;
|
2010-04-01 21:59:19 -07:00
|
|
|
struct attr_event attr;
|
2010-04-01 21:59:20 -07:00
|
|
|
struct event_type_event event_type;
|
2010-04-01 21:59:21 -07:00
|
|
|
struct tracing_data_event tracing_data;
|
2010-04-01 21:59:22 -07:00
|
|
|
struct build_id_event build_id;
|
2009-08-12 01:19:53 -07:00
|
|
|
} event_t;
|
2009-08-12 02:07:25 -07:00
|
|
|
|
2009-11-27 11:29:22 -07:00
|
|
|
void event__print_totals(void);
|
|
|
|
|
perf session: Move kmaps to perf_session
There is still some more work to do to disentangle map creation
from DSO loading, but this happens only for the kernel, and for
the early adopters of perf diff, where this disentanglement
matters most, we'll be testing different kernels, so no problem
here.
Further clarification: right now we create the kernel maps for
the various modules and discontiguous kernel text maps when
loading the DSO, we should do it as a two step process, first
creating the maps, for multiple mappings with the same DSO
store, then doing the dso load just once, for the first hit on
one of the maps sharing this DSO backing store.
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>
LKML-Reference: <1260741029-4430-6-git-send-email-acme@infradead.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-12-13 14:50:29 -07:00
|
|
|
struct perf_session;
|
|
|
|
|
2010-01-07 14:59:40 -07:00
|
|
|
typedef int (*event__handler_t)(event_t *event, struct perf_session *session);
|
|
|
|
|
|
|
|
int event__synthesize_thread(pid_t pid, event__handler_t process,
|
2009-12-13 14:50:24 -07:00
|
|
|
struct perf_session *session);
|
2010-01-07 14:59:40 -07:00
|
|
|
void event__synthesize_threads(event__handler_t process,
|
2009-12-13 14:50:24 -07:00
|
|
|
struct perf_session *session);
|
2010-01-07 14:59:40 -07:00
|
|
|
int event__synthesize_kernel_mmap(event__handler_t process,
|
2010-04-18 22:32:50 -07:00
|
|
|
struct perf_session *session,
|
2010-04-27 17:17:50 -07:00
|
|
|
struct machine *machine,
|
2010-04-18 22:32:50 -07:00
|
|
|
const char *symbol_name);
|
|
|
|
|
perf tools: Encode kernel module mappings in perf.data
We were always looking at the running machine /proc/modules,
even when processing a perf.data file, which only makes sense
when we're doing 'perf record' and 'perf report' on the same
machine, and in close sucession, or if we don't use modules at
all, right Peter? ;-)
Now, at 'perf record' time we read /proc/modules, find the long
path for modules, and put them as PERF_MMAP events, just like we
did to encode the reloc reference symbol for vmlinux. Talking
about that now it is encoded in .pgoff, so that we can use
.{start,len} to store the address boundaries for the kernel so
that when we reconstruct the kmaps tree we can do lookups right
away, without having to fixup the end of the kernel maps like we
did in the past (and now only in perf record).
One more step in the 'perf archive' direction when we'll finally
be able to collect data in one machine and analyse in another.
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>
LKML-Reference: <1263396139-4798-1-git-send-email-acme@infradead.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2010-01-13 08:22:17 -07:00
|
|
|
int event__synthesize_modules(event__handler_t process,
|
2010-04-18 22:32:50 -07:00
|
|
|
struct perf_session *session,
|
2010-04-27 17:17:50 -07:00
|
|
|
struct machine *machine);
|
2009-10-26 14:23:18 -07:00
|
|
|
|
2009-12-13 14:50:24 -07:00
|
|
|
int event__process_comm(event_t *self, struct perf_session *session);
|
|
|
|
int event__process_lost(event_t *self, struct perf_session *session);
|
|
|
|
int event__process_mmap(event_t *self, struct perf_session *session);
|
|
|
|
int event__process_task(event_t *self, struct perf_session *session);
|
2009-11-27 11:29:22 -07:00
|
|
|
|
perf tools: Consolidate symbol resolving across all tools
Now we have a very high level routine for simple tools to
process IP sample events:
int event__preprocess_sample(const event_t *self,
struct addr_location *al,
symbol_filter_t filter)
It receives the event itself and will insert new threads in the
global threads list and resolve the map and symbol, filling all
this info into the new addr_location struct, so that tools like
annotate and report can further process the event by creating
hist_entries in their specific way (with or without callgraphs,
etc).
It in turn uses the new next layer function:
void thread__find_addr_location(struct thread *self, u8 cpumode,
enum map_type type, u64 addr,
struct addr_location *al,
symbol_filter_t filter)
This one will, given a thread (userspace or the kernel kthread
one), will find the given type (MAP__FUNCTION now, MAP__VARIABLE
too in the near future) at the given cpumode, taking vdsos into
account (userspace hit, but kernel symbol) and will fill all
these details in the addr_location given.
Tools that need a more compact API for plain function
resolution, like 'kmem', can use this other one:
struct symbol *thread__find_function(struct thread *self, u64 addr,
symbol_filter_t filter)
So, to resolve a kernel symbol, that is all the 'kmem' tool
needs, its just a matter of calling:
sym = thread__find_function(kthread, addr, NULL);
The 'filter' parameter is needed because we do lazy
parsing/loading of ELF symtabs or /proc/kallsyms.
With this we remove more code duplication all around, which is
always good, huh? :-)
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: John Kacur <jkacur@redhat.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>
LKML-Reference: <1259346563-12568-12-git-send-email-acme@infradead.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-11-27 11:29:23 -07:00
|
|
|
struct addr_location;
|
2009-12-13 14:50:28 -07:00
|
|
|
int event__preprocess_sample(const event_t *self, struct perf_session *session,
|
|
|
|
struct addr_location *al, symbol_filter_t filter);
|
2009-12-06 04:08:24 -07:00
|
|
|
int event__parse_sample(event_t *event, u64 type, struct sample_data *data);
|
perf tools: Consolidate symbol resolving across all tools
Now we have a very high level routine for simple tools to
process IP sample events:
int event__preprocess_sample(const event_t *self,
struct addr_location *al,
symbol_filter_t filter)
It receives the event itself and will insert new threads in the
global threads list and resolve the map and symbol, filling all
this info into the new addr_location struct, so that tools like
annotate and report can further process the event by creating
hist_entries in their specific way (with or without callgraphs,
etc).
It in turn uses the new next layer function:
void thread__find_addr_location(struct thread *self, u8 cpumode,
enum map_type type, u64 addr,
struct addr_location *al,
symbol_filter_t filter)
This one will, given a thread (userspace or the kernel kthread
one), will find the given type (MAP__FUNCTION now, MAP__VARIABLE
too in the near future) at the given cpumode, taking vdsos into
account (userspace hit, but kernel symbol) and will fill all
these details in the addr_location given.
Tools that need a more compact API for plain function
resolution, like 'kmem', can use this other one:
struct symbol *thread__find_function(struct thread *self, u64 addr,
symbol_filter_t filter)
So, to resolve a kernel symbol, that is all the 'kmem' tool
needs, its just a matter of calling:
sym = thread__find_function(kthread, addr, NULL);
The 'filter' parameter is needed because we do lazy
parsing/loading of ELF symtabs or /proc/kallsyms.
With this we remove more code duplication all around, which is
always good, huh? :-)
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Frédéric Weisbecker <fweisbec@gmail.com>
Cc: John Kacur <jkacur@redhat.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Paul Mackerras <paulus@samba.org>
LKML-Reference: <1259346563-12568-12-git-send-email-acme@infradead.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-11-27 11:29:23 -07:00
|
|
|
|
2010-05-14 06:36:42 -07:00
|
|
|
extern const char *event__name[];
|
|
|
|
|
2009-09-24 09:02:18 -07:00
|
|
|
#endif /* __PERF_RECORD_H */
|