From: Namhyung Kim <namhyung@kernel.org>
To: David Carrillo-Cisneros <davidcc@google.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Andi Kleen <andi@firstfloor.org>, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.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: Fri, 28 Apr 2017 12:07:30 +0900 [thread overview]
Message-ID: <CAM9d7cgYk_q1C4ASQ=90m9A4XpHbHJJCD913pk1h1Q7dCBGFcA@mail.gmail.com> (raw)
In-Reply-To: <CALcN6miCRD329i_4UNjhVHOpnxgG6j8L_giLtFc5nmSGn_JQhw@mail.gmail.com>
Hi,
On Fri, Apr 28, 2017 at 9:31 AM, 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.
Yep, currently perf report TUI hides warnings since there's no space
to show them.
>
> $ perf record -e syscalls:sys_enter_mmap some_load
>
> $ perf report --stdio
>
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field addr not found
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field len not found
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field prot not found
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field flags not found
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field fd not found
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field off not found
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field addr not found
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field len not found
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field prot not found
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field flags not found
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field fd not found
> Warning: [syscalls:sys_enter_mmap] eval_num_arg: field off not found
>
> I bisected the warnings to:
> commit d49dadea78624 ("perf tools: Make 'trace' or 'trace_fields'
> sort key default for tracepoint events").
>
> that introduced sorting by trace. The event's format in my example is:
>
> $ cat /sys/kernel/debug/tracing/events/syscalls/sys_enter_socket/format
>
> name: sys_enter_socket
> ID: 1850
> format:
> field:unsigned short common_type; offset:0;
> size:2; signed:0;
> field:unsigned char common_flags; offset:2;
> size:1; signed:0;
> field:unsigned char common_preempt_count; offset:3;
> size:1; signed:0;
> field:int common_pid; offset:4; size:4; signed:1;
>
> print fmt: "family: 0x%08lx, type: 0x%08lx, protocol: 0x%08lx",
> ((unsigned long)(REC->family)), ((unsigned long)(REC->type)),
> ((unsigned long)(REC->protocol))
>
>
> An appears to be correctly parsed by event_read_print in
> tools/lib/tracevent/event-parse.c . Has anyone seen this before?
But I don't see any warning when I run it with --stdio. Could you
show me the format file of sys_enter_mmap?
Thanks,
Namhyung
next prev parent reply other threads:[~2017-04-28 3:08 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
2017-04-30 17:34 ` David Carrillo-Cisneros
2017-04-28 3:07 ` Namhyung Kim [this message]
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='CAM9d7cgYk_q1C4ASQ=90m9A4XpHbHJJCD913pk1h1Q7dCBGFcA@mail.gmail.com' \
--to=namhyung@kernel.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=peterz@infradead.org \
--cc=rostedt@goodmis.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).