Re: [PATCH v3] perf probe: Find compilation directory path for lazy matching

2015-04-13 Thread Masami Hiramatsu
(2015/04/14 8:10), Arnaldo Carvalho de Melo wrote: > Em Fri, Mar 13, 2015 at 02:18:40PM +0900, Naohiro Aota escreveu: >> If we use lazy matching, it failed to open a souce file if perf command >> is invoked outside of compilation directory: >> >> $ perf probe -a '__schedule;clear_*' >> Failed to op

Re: [PATCH v3] perf probe: Find compilation directory path for lazy matching

2015-04-13 Thread Arnaldo Carvalho de Melo
Em Fri, Mar 13, 2015 at 02:18:40PM +0900, Naohiro Aota escreveu: > If we use lazy matching, it failed to open a souce file if perf command > is invoked outside of compilation directory: > > $ perf probe -a '__schedule;clear_*' > Failed to open kernel/sched/core.c: No such file or directory > Err

Re: [PATCH v3] perf probe: Find compilation directory path for lazy matching

2015-03-13 Thread Masami Hiramatsu
(2015/03/13 14:18), Naohiro Aota wrote: > If we use lazy matching, it failed to open a souce file if perf command > is invoked outside of compilation directory: > > $ perf probe -a '__schedule;clear_*' > Failed to open kernel/sched/core.c: No such file or directory > Error: Failed to add events.

[PATCH v3] perf probe: Find compilation directory path for lazy matching

2015-03-12 Thread Naohiro Aota
If we use lazy matching, it failed to open a souce file if perf command is invoked outside of compilation directory: $ perf probe -a '__schedule;clear_*' Failed to open kernel/sched/core.c: No such file or directory Error: Failed to add events. (-2) OTOH, other commands like "probe -L" can solv