[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <044380c5-fce2-3327-d947-af19a33e3087@gmail.com>
Date: Thu, 27 Apr 2017 20:51:28 -0600
From: David Ahern <dsahern@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: David Carrillo-Cisneros <davidcc@...gle.com>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Andi Kleen <andi@...stfloor.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Wang Nan <wangnan0@...wei.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Stephane Eranian <eranian@...gle.com>
Subject: Re: perf report warnings on tracepoint events hidden by ui
On 4/27/17 8:49 PM, Steven Rostedt wrote:
> On Thu, 27 Apr 2017 20:13:43 -0600
> David Ahern <dsahern@...il.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@...gle.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@...ny-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@...ny-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?
Powered by blists - more mailing lists