From: Namhyung Kim <namhyung@gmail.com>
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: Wed, 18 Jun 2014 09:31:59 +0900 [thread overview]
Message-ID: <87sin383cw.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20140616060804.GA9394@stfomichev-desktop.yandex.net> (Stanislav Fomichev's message of "Mon, 16 Jun 2014 10:08:04 +0400")
Hi Stanislav,
On Mon, 16 Jun 2014 10:08:04 +0400, Stanislav Fomichev wrote:
>> It was because, as I said, my system doesn't have pread64 syscall.. you
>> missed to decrease rec_argc when skipping invalid events. :)
> Thanks, missed that!
>
>> 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.
> Did you try it with all patches applied? Because if you have really fast
> IO you can miss it (unless you applied perf timechart: add more options
> to IO mode).
I applied all your three patches.
$ git log --oneline -3
ddba809264f7 perf timechart: add more options to IO mode
81cc94085210 perf timechart: conditionally update start_time on fork
6aea1951c072 perf timechart: implement IO mode
$ perf --version
perf version 3.15.rc4.gddba809
$ perf timechart record -I dd if=/dev/zero of=xxx bs=4k count=10k
10240+0 records in
10240+0 records out
41943040 bytes (42 MB) copied, 0.0533579 s, 786 MB/s
[ perf record: Woken up 16 times to write data ]
[ perf record: Captured and wrote 4.209 MB perf.data (~183881 samples) ]
$ perf timechart
Written 0.1 seconds of trace to output.svg
> Can you somehow share your perf.data with me? I'll check what's going
> on.
https://git.kernel.org/cgit/linux/kernel/git/namhyung/linux-perf.git/plain/tools/perf/perf.timechart.data?h=perf/tmp
Thanks,
Namhyung
next prev parent reply other threads:[~2014-06-18 0:32 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
2014-06-16 6:08 ` Stanislav Fomichev
2014-06-18 0:31 ` Namhyung Kim [this message]
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=87sin383cw.fsf@sejong.aot.lge.com \
--to=namhyung@gmail.com \
--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