From: Namhyung Kim <namhyung@kernel.org>
To: Stanislav Fomichev <stfomichev@yandex-team.ru>
Cc: acme@kernel.org, artagnon@gmail.com, jolsa@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] perf timechart: implement IO mode
Date: Thu, 12 Jun 2014 09:59:29 +0900 [thread overview]
Message-ID: <87ppif9c3y.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1402412694-5996-2-git-send-email-stfomichev@yandex-team.ru> (Stanislav Fomichev's message of "Tue, 10 Jun 2014 19:04:52 +0400")
Hi Stanislav,
On Tue, 10 Jun 2014 19:04:52 +0400, Stanislav Fomichev wrote:
> In IO mode timechart shows any disk/network activity.
[SNIP]
> +Record system-wide IO events:
> +
> + $ perf timechart record -I
I got a segfault here:
Core was generated by `perf timechart record -I'.
Program terminated with signal 11, Segmentation fault.
#0 parse_options_step (ctx=ctx@entry=0x7fff6dcd8ef0,
options=options@entry=0x587de0, usagestr=usagestr@entry=0x588900)
at util/parse-options.c:353
353 if (*arg != '-' || !arg[1]) {
Missing separate debuginfos, use: debuginfo-install glibc-2.17-9.fc20.x86_64 nss-softokn-freebl-3.15-1.fc20.x86_64 numactl-libs-2.0.7-6.fc17.x86_64
(gdb) bt
#0 parse_options_step (ctx=ctx@entry=0x7fff6dcd8ef0, options=options@entry=
0x587de0, usagestr=usagestr@entry=0x588900) at util/parse-options.c:353
#1 0x0000000000465cf4 in parse_options_subcommand (argc=argc@entry=197,
argv=argv@entry=0x13fd6d0, options=options@entry=0x587de0,
subcommands=subcommands@entry=0x0, usagestr=usagestr@entry=0x588900,
flags=flags@entry=2) at util/parse-options.c:462
#2 0x0000000000465f54 in parse_options (argc=argc@entry=197, argv=argv@entry=
0x13fd6d0, options=options@entry=0x587de0, usagestr=usagestr@entry=
0x588900, flags=flags@entry=2) at util/parse-options.c:492
#3 0x0000000000429ef8 in cmd_record (argc=argc@entry=197, argv=argv@entry=
0x13fd6d0, prefix=prefix@entry=0x0) at builtin-record.c:894
#4 0x0000000000434c59 in timechart__io_record (argv=0x7fff6dcdc270, argc=0)
at builtin-timechart.c:1756
#5 cmd_timechart (argc=0, argv=0x7fff6dcdc270, prefix=<optimized out>)
at builtin-timechart.c:1957
#6 0x000000000041b603 in run_builtin (p=p@entry=0x7fa230, argc=argc@entry=3,
argv=argv@entry=0x7fff6dcdc270) at perf.c:319
#7 0x000000000041ae82 in handle_internal_command (argv=0x7fff6dcdc270, argc=3)
at perf.c:376
#8 run_argv (argv=0x7fff6dcdc060, argcp=0x7fff6dcdc06c) at perf.c:420
#9 main (argc=3, argv=0x7fff6dcdc270) at perf.c:534
It was because, as I said, my system doesn't have pread64 syscall.. you
missed to decrease rec_argc when skipping invalid events. :)
> +
> + then generate timechart:
> +
> + $ perf timechart
After fixing the problem, I could run timechart and generate an
output.svg file. But it doesn't show any IO activity.. process info was
there in grey boxes (rect.process3) but no color boxes. I also tried
recording with ping and dd, but the result was same. I suspect it's
because of some mis-calculation of position or size of the boxes.
Thanks,
Namhyung
next prev parent reply other threads:[~2014-06-12 0:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 15:04 [PATCH v2 0/3] perf timechart io mode Stanislav Fomichev
2014-06-10 15:04 ` [PATCH 1/3] perf timechart: implement IO mode Stanislav Fomichev
2014-06-12 0:59 ` Namhyung Kim [this message]
2014-06-16 6:08 ` Stanislav Fomichev
2014-06-18 0:31 ` Namhyung Kim
2014-06-18 9:00 ` Stanislav Fomichev
2014-06-19 0:30 ` Namhyung Kim
2014-06-19 9:58 ` Stanislav Fomichev
2014-06-19 12:18 ` Stanislav Fomichev
2014-06-19 12:38 ` Namhyung Kim
2014-06-10 15:04 ` [PATCH 2/3] perf timechart: conditionally update start_time on fork Stanislav Fomichev
2014-06-10 15:04 ` [PATCH 3/3] perf timechart: add more options to IO mode Stanislav Fomichev
2014-06-12 1:03 ` Namhyung Kim
2014-06-16 6:15 ` Stanislav Fomichev
2014-06-18 0:33 ` Namhyung Kim
-- strict thread matches above, loose matches on Subject: below --
2014-06-19 12:23 [PATCH v3 0/3] perf timechart io mode Stanislav Fomichev
2014-06-19 12:23 ` [PATCH 1/3] perf timechart: implement IO mode Stanislav Fomichev
2014-06-20 1:04 ` Namhyung Kim
2014-06-20 9:19 ` Stanislav Fomichev
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=87ppif9c3y.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=artagnon@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stfomichev@yandex-team.ru \
/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