linux-kernel - Re: Does perf inject preserve call chain data?

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:	Sat, 9 Jun 2012 13:05:47 -0300
From:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
To:	Andi Kleen <ak@...ux.intel.com>
Cc:	Tim Chen <tim.c.chen@...ux.intel.com>,
	David Ahern <dsahern@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: Does perf inject preserve call chain data?

Em Fri, Jun 08, 2012 at 12:52:15PM -0700, Andi Kleen escreveu:
> > > > # ./perf record -a -g -o - sleep 5 |perf inject -v -b  | perf report -g  -i -

> Since this is a common pattern with files, but files are often slow
> and too big, it would be nice if perf had a standard alias that
> started this pipeline.

I think this is just a variation for perf top, no? I.e. something like:

# perf top -a -G sleep 5

Where it would figure out that since a workload was specified, it should
just not be refreshing the screen every N seconds but wait till the
workload to finish and then present the results, without setting up any
perf.data files.

It could as well show intermediate results every N seconds, but not decay
the older samples, which should be even nicer.

For workloads where there is output it could spawn another term, in the
background perhaps, that the user could switch to to see the samples
collected while the workload runs.

That looks like a step in the direction of more integration of the
tools, i.e. record + report (top being report+refreshes) + annotate.

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