linux-kernel - Re: [PATCH 1/3] perf tools: Record total sampling time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 2 Dec 2013 15:51:16 -0300
From:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
To:	Namhyung Kim <namhyung@...nel.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Stephane Eranian <eranian@...gle.com>,
	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>,
	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

Em Tue, Dec 03, 2013 at 12:05:49AM +0900, Namhyung Kim escreveu:
> Hi Ingo,
> 
> 2013-12-02 (월), 13:45 +0100, Ingo Molnar:
> > * 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.
> 
> Yeah, it'd be great if we can share same code in the end.

I guess we'll basically just process all samples, accumulating stuff
where the builtin-stat code finds them, in struct perf_evsel, then just
hand it to that code.

- Arnaldo
--
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/