[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87sin383cw.fsf@sejong.aot.lge.com>
Date: Wed, 18 Jun 2014 09:31:59 +0900
From: Namhyung Kim <namhyung@...il.com>
To: Stanislav Fomichev <stfomichev@...dex-team.ru>
Cc: acme@...nel.org, artagnon@...il.com, jolsa@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] perf timechart: implement IO mode
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists