From: David Ahern <dsahern@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@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>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH 1/2] perf test: Silence tracepoint event failures
Date: Mon, 19 Oct 2015 10:08:38 -0600 [thread overview]
Message-ID: <56251586.3010908@gmail.com> (raw)
In-Reply-To: <1445268229-1601-1-git-send-email-namhyung@kernel.org>
On 10/19/15 9:23 AM, Namhyung Kim wrote:
> 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.
>
-----8<-----
>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
> tools/perf/tests/openat-syscall-all-cpus.c | 2 +-
> tools/perf/tests/openat-syscall-tp-fields.c | 2 +-
> tools/perf/tests/openat-syscall.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
Acked-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2015-10-19 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 15:23 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 ` David Ahern [this message]
2015-10-19 17:57 ` [PATCH 1/2] perf test: Silence tracepoint event failures Arnaldo Carvalho de Melo
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=56251586.3010908@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--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
Powered by JetHome