[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a0b768ec-6f46-0ca9-7525-a19ee9ba04ad@gmail.com>
Date: Thu, 27 Apr 2017 20:13:43 -0600
From: David Ahern <dsahern@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>,
David Carrillo-Cisneros <davidcc@...gle.com>
Cc: 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 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.
See the note I put into tools/perf/builtin-trace.c:
static struct perf_evsel *perf_evsel__syscall_newtp(const char
*direction, void *handler)
{
struct perf_evsel *evsel = perf_evsel__newtp("raw_syscalls",
direction);
/* older kernel (e.g., RHEL6) use syscalls:{enter,exit} */
if (IS_ERR(evsel))
evsel = perf_evsel__newtp("syscalls", direction);
Are you running top of tree perf on RHEL6?
Powered by blists - more mailing lists