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]
Message-ID: <87sjch5xpf.fsf@sejong.aot.lge.com>
Date:	Tue, 24 Jul 2012 18:13:00 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Stephane Eranian <eranian@...gle.com>,
	Jiri Olsa <jolsa@...hat.com>,
	Ulrich Drepper <drepper@...il.com>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: [RFC/PATCHSET 00/12] perf report: Add support to event group viewing (v1)

On Tue, 24 Jul 2012 18:01:21 +0900, Namhyung Kim wrote:
> Hi all,
>
> This is a patchset to support event grouping on perf report.
>
> It depends on other patches like refactoring hist print [1],
> processing file header feature [2] and (obviously) Jiri's event group
> management [3]. All of this need to be reviewed though. ;)
>
> The basic idea is move group member's hist entries to a leader, and
> sort/collapse them on the leader's tree. The leader will have all of
> group members' stat in it. The output is sorted by the leader's period
> and in turn first child and so on.
>
> To use it, 'perf record' should group events when recording. And then
> perf report parses the saved command line and reconstruct the group
> relation. Currently only the '-e { event1,event2 }' syntax is supported
> (i.e. --group option is *NOT* supported) to make things easy. But it'd
> not be that hard to support --group also.
>
> But I think re-using event parsing routine (at least, in its current
> form) has some problems especially if perf report will not run on the
> same machine that runs perf record. I cannot find a better way than
> extending/changing the perf file format to let perf record know about

s/perf record/perf report/

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ