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  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:	Thu, 17 Jul 2014 10:40:11 +0200
From:	Peter Zijlstra <>
To:	Namhyung Kim <>
Cc:	Arnaldo Carvalho de Melo <>,
	Ingo Molnar <>,
	Paul Mackerras <>,
	Namhyung Kim <>,
	LKML <>,
	Jiri Olsa <>, Minchan Kim <>
Subject: Re: [PATCH] perf stat: Pass PERF_STAT_RUN environment variable for
 each run

On Thu, Jul 17, 2014 at 05:31:14PM +0900, Namhyung Kim wrote:
> Hi Peter,
> On Thu, Jul 17, 2014 at 5:26 PM, Peter Zijlstra <> wrote:
> > On Thu, Jul 17, 2014 at 05:21:06PM +0900, Namhyung Kim wrote:
> >> When perf stat runs multiple times via -r option, it's sometimes
> >> useful for a workload to know which run it executing.  So pass new
> >> PERF_STAT_RUN environment variable to the workload for each run
> >> (starting from 1).
> >
> > This seems counter intuitive, runs should be _identical_ otherwise
> > there's no point. That means the workload should very much _not_ know
> > these things.
> But I think it can be useful if a workload wants to save logfiles
> based on the iteration number for example.  If it doesn't want, it can
> just ignore. :)

That's the wrong way around. Also, there's --pre and --post hooks to
preserve logfiles if you really have to do that kind of thing.

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists