[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131202124527.GB22212@gmail.com>
Date: Mon, 2 Dec 2013 13:45:27 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>,
Stephane Eranian <eranian@...gle.com>
Cc: Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Namhyung Kim <namhyung.kim@....com>,
LKML <linux-kernel@...r.kernel.org>,
Jiri Olsa <jolsa@...hat.com>, David Ahern <dsahern@...il.com>,
Stephane Eranian <eranian@...gle.com>,
Andi Kleen <andi@...stfloor.org>,
Pekka Enberg <penberg@...nel.org>,
Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 1/3] perf tools: Record total sampling time
* Namhyung Kim <namhyung@...nel.org> wrote:
> From: Namhyung Kim <namhyung.kim@....com>
>
> It's sometimes useful to see total sampling or elapsed time with
> normal performance result. To do that, record first and last sample
> time for each evsel and to display it in the header (--stdio only for
> now).
>
> $ perf record -a sleep 1
> $ perf report --stdio
> ...
> # Samples: 4K of event 'cycles'
> # Event count (approx.): 4087481688
> # Total sampling time : 1.001260 (sec)
Btw., would it make sense to output it using the 'perf stat' print-out
machinery?
If the 'count' of every event sampled is saved in the perf.data,
including elapsed time, at the beginning and at the end, then all
information is there to output things in perf stat style.
( It might even make sense to save two more timestamps: rusage stime
and utime - that way the output could be made /usr/bin/time-alike. )
Also I think there is some related existing functionality, I think
Stephane added a way to essentially do non-sampling 'perf stat' via
perf record - but the details escape me, I think it was related to the
-n option?
So what we want here is in essence a sampling mode that can record and
report all the absolute counts as well.
Thanks,
Ingo
--
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