From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH 1/2] perf test: Silence tracepoint event failures
Date: Mon, 19 Oct 2015 14:57:06 -0300 [thread overview]
Message-ID: <20151019175706.GA3215@kernel.org> (raw)
In-Reply-To: <1445268229-1601-1-git-send-email-namhyung@kernel.org>
Em Tue, Oct 20, 2015 at 12:23:48AM +0900, Namhyung Kim escreveu:
> Currently, when perf test is run by a normal user, it'll fail to access
> tracepoint events. However the output is somewhat messy since it tries
> to be nice with long error messages and hints. IMHO it's not needed
> for 'perf test' by default and AFAIK the perf test uses pr_debug()
> rather than pr_err() for such messages so that one can use -v option to
> see further details on failed testcases if needed.
>
> Before:
> $ perf test
> 1: vmlinux symtab matches kallsyms : FAILED!
> 2: detect openat syscall event :Error:
> No permissions to read
> /sys/kernel/debug/tracing/events/syscalls/sys_enter_openat
> Hint: Try 'sudo mount -o remount,mode=755 /sys/kernel/debug/tracing'
> FAILED!
> 3: detect openat syscall event on all cpus :Error:
> No permissions to read
> /sys/kernel/debug/tracing/events/syscalls/sys_enter_openat
> Hint: Try 'sudo mount -o remount,mode=755 /sys/kernel/debug/tracing'
> FAILED!
> ...
>
> After:
> $ perf test
> 1: vmlinux symtab matches kallsyms : FAILED!
> 2: detect openat syscall event : FAILED!
> 3: detect openat syscall event on all cpus : FAILED!
> ...
>
> $ perf test -v 2
> 2: detect openat syscall event :
> --- start ---
> test child forked, pid 30575
> Error: No permissions to read
> /sys/kernel/debug/tracing/events/syscalls/sys_enter_openat
> Hint: Try 'sudo mount -o remount,mode=755 /sys/kernel/debug/tracing'
>
> test child finished with -1
> ---- end ----
> detect openat syscall event: FAILED!
Here I get useless informational messages about registering plugins,
guess those should move to pr_debug2, no?
Anyway, applying the patch, the common case is to run 'perf test'.
[acme@zoo linux]$ perf test -v 2
2: detect openat syscall event :
--- start ---
test child forked, pid 22866
registering plugin: /home/acme/.traceevent/plugins/plugin_function.so
registering plugin: /home/acme/.traceevent/plugins/plugin_mac80211.so
registering plugin: /home/acme/.traceevent/plugins/plugin_scsi.so
registering plugin: /home/acme/.traceevent/plugins/plugin_hrtimer.so
registering plugin: /home/acme/.traceevent/plugins/plugin_sched_switch.so
registering plugin: /home/acme/.traceevent/plugins/plugin_cfg80211.so
registering plugin: /home/acme/.traceevent/plugins/plugin_kmem.so
registering plugin: /home/acme/.traceevent/plugins/plugin_kvm.so
registering plugin: /home/acme/.traceevent/plugins/plugin_xen.so
registering plugin: /home/acme/.traceevent/plugins/plugin_jbd2.so
Error: No permissions to read /sys/kernel/debug/tracing/events/syscalls/sys_enter_openat
Hint: Try 'sudo mount -o remount,mode=755 /sys/kernel/debug/tracing'
test child finished with -1
---- end ----
detect openat syscall event: FAILED!
[acme@zoo linux]$
next prev parent reply other threads:[~2015-10-19 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 15:23 [PATCH 1/2] perf test: Silence tracepoint event failures Namhyung Kim
2015-10-19 15:23 ` [PATCH 2/2] perf test: Suppress libtraceevent warnings Namhyung Kim
2015-10-19 16:09 ` David Ahern
2015-10-19 18:00 ` Arnaldo Carvalho de Melo
2015-10-20 7:42 ` [tip:perf/core] " tip-bot for Namhyung Kim
2015-10-19 16:08 ` [PATCH 1/2] perf test: Silence tracepoint event failures David Ahern
2015-10-19 17:57 ` Arnaldo Carvalho de Melo [this message]
2015-10-20 7:42 ` [tip:perf/core] " tip-bot for Namhyung Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151019175706.GA3215@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=wangnan0@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).