From: Steven Rostedt <rostedt@goodmis.org>
To: David Ahern <dsahern@gmail.com>
Cc: David Carrillo-Cisneros <davidcc@google.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Andi Kleen <andi@firstfloor.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Wang Nan <wangnan0@huawei.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: perf report warnings on tracepoint events hidden by ui
Date: Thu, 27 Apr 2017 22:54:39 -0400 [thread overview]
Message-ID: <20170427225439.079e26a7@gandalf.local.home> (raw)
In-Reply-To: <044380c5-fce2-3327-d947-af19a33e3087@gmail.com>
On Thu, 27 Apr 2017 20:51:28 -0600
David Ahern <dsahern@gmail.com> wrote:
> On 4/27/17 8:49 PM, Steven Rostedt wrote:
> > On Thu, 27 Apr 2017 20:13:43 -0600
> > David Ahern <dsahern@gmail.com> wrote:
> >
> >> On 4/27/17 7:41 PM, Steven Rostedt wrote:
> >>> On Thu, 27 Apr 2017 19:31:12 -0500
> >>> David Carrillo-Cisneros <davidcc@google.com> wrote:
> >>>
> >>>> When processing tracepoint events, perf report outputs warnings about
> >>>> field not founds. The warnings are usually hidden by perf report UI
> >>>> and appear when using the --stdio option. e.g.
> >>>>
> >>>> $ perf record -e syscalls:sys_enter_mmap some_load
> >>
> >> '-e syscalls' vs raw_syscalls suggests an older kernel -- like RHEL6.
> >
> > New kernels have both syscalls and raw_syscalls. The raw_syscalls are
> > the true tracepoints that the syscalls use. His option works on
> > 4.11-rc8.
>
>
> What's old is new again?
>
> root@kenny-jessie4:~# uname -a
> Linux kenny-jessie4 4.11.0-rc8+ #258 SMP Thu Apr 27 08:36:06 PDT 2017
> x86_64 GNU/Linux
>
> root@kenny-jessie4:~# perf list | grep syscalls
> raw_syscalls:sys_enter [Tracepoint event]
> raw_syscalls:sys_exit [Tracepoint event]
>
>
> Is an option needed to enable syscalls vs raw_syscalls?
Yep!
CONFIG_FTRACE_SYSCALLS=y
-- Steve
next prev parent reply other threads:[~2017-04-28 2:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 0:31 perf report warnings on tracepoint events hidden by ui David Carrillo-Cisneros
2017-04-28 1:41 ` Steven Rostedt
2017-04-28 2:13 ` David Ahern
2017-04-28 2:49 ` Steven Rostedt
2017-04-28 2:51 ` David Ahern
2017-04-28 2:54 ` Steven Rostedt [this message]
2017-04-30 17:34 ` David Carrillo-Cisneros
2017-04-28 3:07 ` Namhyung Kim
2017-04-30 17:32 ` David Carrillo-Cisneros
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=20170427225439.079e26a7@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=davidcc@google.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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