perf ftrace: Several perf ftrace:function event fixes
Subsystems (2)
Jiri Olsa
reviewerv2 cover perf ftrace: Several perf ftrace:function event fixes
hi,
sending few fixes for perf ftrace:function event handling. It's v2 for following original post:
http://marc.info/?l=linux-kernel&m=144846634815636&w=2
v2 changes:
- using ftrace_ops::private to store event pointer
- moving attr::exclude_kernel check into event init processing
thanks,
jirka
---
Jiri Olsa (3):
ftrace: Check sample types only for sampling events
perf: Move exclude_kernel tracepoint check to init event perf ftrace: Use ftrace_ops::private to store event pointer
include/linux/perf_event.h | 3 +++ kernel/events/core.c | 30 +++++++++++++++++++++++++----- kernel/trace/trace_event_perf.c | 28 +++++++++++++++++++--------- 3 files changed, 47 insertions(+), 14 deletions(-)
Jiri Olsa
reviewerPATCH v2 1/3 ftrace: Check sample types only for sampling events
Currently we check sample type for ftrace:function event even if it's not created as sampling event. That prevents creating ftrace_function event in counting mode.
Making sure we check sample types only for sampling events.
Before:
$ sudo perf stat -e ftrace:function ls ...
Performance counter stats for 'ls':
<not supported> ftrace:function
0.001983662 seconds time elapsed
After:
$ sudo perf stat -e ftrace:function ls ...
Performance counter stats for 'ls':
44,498 ftrace:function
0.037534722 seconds time elapsed--- kernel/trace/trace_event_perf.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
kernel/trace/trace_event_perf.c +2 -2
@@ -52,14 +52,14 @@ static int perf_trace_event_perm(struct trace_event_call *tp_event,* event, due to issues with page faults while tracing page * fault handler and its overall trickiness nature. */ -if (!p_event->attr.exclude_callchain_user) +if (is_sampling_event (p_event) && !p_event->attr.exclude_callchain_user)return -EINVAL ;/* * Same reason to disable user stack dump as for user space * callchains above. */ -if (p_event->attr.sample_type &PERF_SAMPLE_STACK_USER ) +if (is_sampling_event (p_event) && p_event->attr.sample_type &PERF_SAMPLE_STACK_USER )return -EINVAL ; }
Signature · 1 line
2.4.3
Jiri Olsa
reviewerPATCH v2 2/3 perf: Move exclude_kernel tracepoint check to init event
In reply to Jiri OlsaWe suppress events with attr::exclude_kernel set when the event is generated, so following capture will give no warning and produce no data:
$ sudo perf record -e sched:sched_switch:u ls $ sudo /perf script | wc -l 0
Checking the attr::exclude_kernel at the event init time and failing right away:
$ sudo perf record -e sched:sched_switch:u ls Error: The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event (sched:sched_switch). /bin/dmesg may provide additional information. No CONFIG_PERF_EVENTS=y kernel support configured?
--- kernel/events/core.c | 5 ----- kernel/trace/trace_event_perf.c | 15 +++++++++++++++ 2 files changed, 15 insertions(+), 5 deletions(-)
kernel/events/core.c +0 -5
@@ -6938,11 +6938,6 @@ static int perf_tp_event_match(struct perf_event *event, {if (event->hw.state &PERF_HES_STOPPED )return 0 ; -/* -* All tracepoints are from kernel-space. -*/ -if (event->attr.exclude_kernel) -return 0 ;if (!perf_tp_filter_match (event, data))return 0 ;
kernel/trace/trace_event_perf.c +15 -0
@@ -182,11 +182,26 @@ static void perf_trace_event_close(struct perf_event *p_event) tp_event->class->reg (tp_event,TRACE_REG_PERF_CLOSE , p_event); } +static int perf_trace_event_attr (struct perf_event *event) +{ +/* +* All tracepoints are from kernel-space. +*/ +if (event->attr.exclude_kernel) +return -EINVAL ; + +return 0 ; +} +static int perf_trace_event_init (struct trace_event_call *tp_event,struct perf_event *p_event) {int ret; + ret =perf_trace_event_attr (p_event); +if (ret) +return ret; + ret =perf_trace_event_perm (tp_event, p_event);if (ret)return ret;
Signature · 1 line
2.4.3
Arnaldo Carvalho de Melo
maintainerRe: [PATCH 2/3] perf: Move exclude_kernel tracepoint check to init event
Em Thu, Nov 26, 2015 at 08:34:48PM +0100, Jiri Olsa escreveu:
Quoted 10 lines
We suppress events with
attr::exclude_kernelset when the event is generated, so following capture will give no warning and produce no data:$ sudo perf record -e sched:sched_switch:u ls $ sudo /perf script | wc -l 0Checking the
attr::exclude_kernelat the event init time and failing right away:
We can as well provide a better warning in the tooling side and don't even ask this nonsensical combo to the kernel, right?
Arguably the kernel was doing what was asked for, its just that no sched:sched_switch took place while in user space... ;-)
- Arnaldo
Quoted 61 lines
$ sudo perf record -e sched:sched_switch:u ls Error: The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event (sched:sched_switch). /bin/dmesg may provide additional information. No CONFIG_PERF_EVENTS=y kernel support configured?Signed-off-by Jiri Olsa <[email protected]>--- kernel/events/core.c | 5 ----- kernel/trace/trace_event_perf.c | 15 +++++++++++++++ 2 files changed, 15 insertions(+), 5 deletions(-)kernel/events/core.c +0
-5@@ -6938,11 +6938,6 @@ static int perf_tp_event_match(struct perf_event *event, {if (event->hw.state &PERF_HES_STOPPED )return 0 ; -/* -* All tracepoints are from kernel-space. -*/ -if (event->attr.exclude_kernel) -return 0 ;if (!perf_tp_filter_match (event, data))return 0 ;kernel/trace/trace_event_perf.c +15
-0@@ -182,11 +182,26 @@ static void perf_trace_event_close(struct perf_event *p_event) tp_event->class->reg (tp_event,TRACE_REG_PERF_CLOSE , p_event); } +static int perf_trace_event_attr (struct perf_event *event) +{ +/* +* All tracepoints are from kernel-space. +*/ +if (event->attr.exclude_kernel) +return -EINVAL ; + +return 0 ; +} +static int perf_trace_event_init (struct trace_event_call *tp_event,struct perf_event *p_event) {int ret; + ret =perf_trace_event_attr (p_event); +if (ret) +return ret; + ret =perf_trace_event_perm (tp_event, p_event);if (ret)return ret;Signature · 1 line
2.4.3
Re: [PATCH 2/3] perf: Move exclude_kernel tracepoint check to init event
Quoted 9 lines · Arnaldo Carvalho de Melo
Em Thu, Nov 26, 2015 at 08:34:48PM +0100, Jiri Olsa escreveu:
Quoted 8 lines
We suppress events with
attr::exclude_kernelset when the event is generated, so following capture will give no warning and produce no data:$ sudo perf record -e sched:sched_switch:u ls $ sudo /perf script | wc -l 0
Quoted 5 lines
Quoted 2 lines
Checking the
attr::exclude_kernelat the event init time and failing right away:We can as well provide a better warning in the tooling side and don't even ask this nonsensical combo to the kernel, right?
yep.. I'll update my todo ;-)
Quoted 3 lines
Arguably the kernel was doing what was asked for, its just that no sched:sched_switch took place while in user space... ;-)
I think it's better to fail like that.. rather than spending time on figuring why my test did not give me any data ;-)
jirka
Arnaldo Carvalho de Melo
maintainerRe: [PATCH 2/3] perf: Move exclude_kernel tracepoint check to init event
Em Thu, Nov 26, 2015 at 08:49:10PM +0100, Jiri Olsa escreveu:
Quoted 10 lines · Arnaldo Carvalho de Melo
Quoted 9 lines
Em Thu, Nov 26, 2015 at 08:34:48PM +0100, Jiri Olsa escreveu:
Quoted 8 lines
We suppress events with
attr::exclude_kernelset when the event is generated, so following capture will give no warning and produce no data:$ sudo perf record -e sched:sched_switch:u ls $ sudo /perf script | wc -l 0
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
Checking the
attr::exclude_kernelat the event init time and failing right away:We can as well provide a better warning in the tooling side and don't even ask this nonsensical combo to the kernel, right?
yep.. I'll update my todo ;-)
Thanks!
Quoted 5 lines
Quoted 2 lines
Arguably the kernel was doing what was asked for, its just that no sched:sched_switch took place while in user space... ;-)
I think it's better to fail like that.. rather than spending time on figuring why my test did not give me any data ;-)
Up to peterz ;-)
- Arnaldo
Jiri Olsa
reviewerPATCH v2 3/3 perf ftrace: Use ftrace_ops::private to store event pointer
In reply to Jiri OlsaHaving following commands running concurently:
# perf record -e ftrace:function -a -o krava.data sleep 10 # perf record -e ftrace:function --filter 'ip == SyS_read' ls
will endup in the latter one failing on the filter rules and store all functions (in perf.data) as instructed by the first record instead of just SyS_read records.
The reason is that we don't check the ftrace_ops that triggered the event with event's ftrace_ops. Hence once running together the event from latter perf will get all the data of the event from the first one.
Fixing this by using ftrace_ops::private value to keep the perf_event pointer. This way we don't need to search for triggered event (as tracepoint handler does) and directly store sample.
--- include/linux/perf_event.h | 3 +++ kernel/events/core.c | 25 +++++++++++++++++++++++++ kernel/trace/trace_event_perf.c | 9 ++------- 3 files changed, 30 insertions(+), 7 deletions(-)
include/linux/perf_event.h +3 -0
@@ -1009,6 +1009,9 @@ extern void perf_tp_event(u64 addr, u64 count, void *record, int entry_size, struct pt_regs *regs, struct hlist_head *head, int rctx, struct task_struct *task); +void perf_function_event (struct perf_event *event, +void *record,int entry_size, +struct pt_regs *regs,int rctx);extern void perf_bp_event (struct perf_event *event,void *data);#ifndef perf_misc_flags
kernel/events/core.c +25 -0
@@ -7103,6 +7103,31 @@ static void perf_event_free_bpf_prog(struct perf_event *event) } } +#ifdef CONFIG_FUNCTION_TRACER +void perf_function_event (struct perf_event *event, +void *record,int entry_size, +struct pt_regs *regs,int rctx) + +{ +struct perf_sample_data data; +struct perf_raw_record raw = { + .size = entry_size, + .data = record, + }; + +if (event->hw.state &PERF_HES_STOPPED ) + goto out; + +perf_sample_data_init (&data,0 ,0 ); + data.raw = &raw; + +perf_swevent_event (event,1 , &data, regs); + +out: +perf_swevent_put_recursion_context (rctx); +} +#endif /* CONFIG_FUNCTION_TRACER */ +#else static inline void perf_tp_register (void )
kernel/trace/trace_event_perf.c +2 -7
@@ -318,14 +318,9 @@ perf_ftrace_function_call(unsigned long ip, unsigned long parent_ip, struct ftrace_ops *ops, struct pt_regs *pt_regs) { struct ftrace_entry *entry; -struct hlist_head *head;struct pt_regs regs;int rctx; - head =this_cpu_ptr (event_function.perf_events); -if (hlist_empty (head)) -return ; -#define ENTRY_SIZE (ALIGN(sizeof(struct ftrace_entry) + sizeof(u32), \ sizeof(u64)) - sizeof(u32))
@@ -339,8 +334,7 @@ perf_ftrace_function_call(unsigned long ip, unsigned long parent_ip, entry->ip = ip; entry->parent_ip = parent_ip; -perf_trace_buf_submit (entry,ENTRY_SIZE , rctx,0 , -1 , ®s, head,NULL ); +perf_function_event (ops->private, entry,ENTRY_SIZE , ®s, rctx);#undef ENTRY_SIZE }
@@ -349,6 +343,7 @@ static int perf_ftrace_function_register(struct perf_event *event) {struct ftrace_ops *ops = &event->ftrace_ops; + ops->private = event; ops->flags |=FTRACE_OPS_FL_CONTROL ; ops->func = perf_ftrace_function_call;return register_ftrace_function (ops);
Signature · 1 line
2.4.3