From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>
Cc: Jiri Olsa <jolsa@kernel.org>, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Adrian Hunter <adrian.hunter@intel.com>,
David Ahern <dsahern@gmail.com>,
Hendrick Brueckner <brueckner@linux.vnet.ibm.com>,
Namhyung Kim <namhyung@kernel.org>,
Noel Grandin <noelgrandin@gmail.com>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [RFC 0/5] per-event settings fixes
Date: Tue, 16 Jan 2018 12:38:05 -0300 [thread overview]
Message-ID: <20180116153805.GD16107@kernel.org> (raw)
In-Reply-To: <5e418aa0-d966-59d4-f024-a5fc61500f8d@linux.vnet.ibm.com>
Em Tue, Jan 16, 2018 at 04:27:52PM +0100, Thomas-Mich Richter escreveu:
> --- ::1 ping statistics ---
> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> rtt min/avg/max/mdev = 0.047/0.047/0.047/0.000 ms
> 0.000 probe_libc:inet_pton:(3ffb4bc2060))
> [root@s8360047 perf]#
>
> Test fails, I would have expected some callchain output.
>
> [root@s8360047 perf]# ./perf trace --no-syscalls --call-graph dwarf --max-stack 4
> -e probe_libc:inet_pton/max-stack=3/ ping -6 -c 1 ::1
> PING ::1(::1) 56 data bytes
> 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.055 ms
>
> --- ::1 ping statistics ---
> 1 packets transmitted, 1 received, 0% packet loss, time 0ms
> rtt min/avg/max/mdev = 0.055/0.055/0.055/0.000 ms
> 0.000 probe_libc:inet_pton:(3ff7e6c2060))
> [root@s8360047 perf]#
>
> Test fails, I would have expected some callchain output.
>
> It looks like /max-stack=3/ without ,call-graph=dwarf
> does not trigger the stack unwinding.
Ok, will work on those, then redo all the tests you did, grr, tricky
stuff.
- Arnaldo
prev parent reply other threads:[~2018-01-16 15:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 14:24 [RFC 0/5] per-event settings fixes Arnaldo Carvalho de Melo
2018-01-16 14:24 ` [PATCH 1/5] perf callchain: Fix attr.sample_max_stack setting Arnaldo Carvalho de Melo
2018-01-16 14:24 ` [PATCH 2/5] perf unwind: Do not look at globals Arnaldo Carvalho de Melo
2018-01-16 15:19 ` Jiri Olsa
2018-01-16 15:36 ` Arnaldo Carvalho de Melo
2018-01-16 18:26 ` Arnaldo Carvalho de Melo
2018-01-16 19:49 ` Jiri Olsa
2018-01-16 20:05 ` Arnaldo Carvalho de Melo
2018-01-17 5:34 ` Namhyung Kim
2018-01-17 8:23 ` Jiri Olsa
2018-01-17 16:33 ` [tip:perf/core] perf unwind: Do not look just at the global callchain_param.record_mode tip-bot for Arnaldo Carvalho de Melo
2018-01-16 19:30 ` [PATCH 2/5] perf unwind: Do not look at globals Jiri Olsa
2018-01-16 19:45 ` Arnaldo Carvalho de Melo
2018-01-16 19:55 ` Jiri Olsa
2018-01-16 20:07 ` Arnaldo Carvalho de Melo
2018-01-16 14:24 ` [PATCH 3/5] perf trace: Setup DWARF callchains for non-syscall events when --max-stack is used Arnaldo Carvalho de Melo
2018-01-16 14:24 ` [PATCH 4/5] perf trace: Allow overriding global --max-stack per event Arnaldo Carvalho de Melo
2018-01-16 14:24 ` [PATCH 5/5] perf callchains: Ask for PERF_RECORD_MMAP for data mmaps for DWARF unwinding Arnaldo Carvalho de Melo
2018-01-16 15:27 ` [RFC 0/5] per-event settings fixes Thomas-Mich Richter
2018-01-16 15:38 ` Arnaldo Carvalho de Melo [this message]
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=20180116153805.GD16107@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=noelgrandin@gmail.com \
--cc=tmricht@linux.vnet.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.