linux-kernel - Re: [PATCH] perf stat: Pass PERF_STAT_RUN environment variable for each run

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: <CAM9d7ciELhfJwdNBSJPCJcrVr43+hs+80m-FK7bE1mkuBcv0yQ@mail.gmail.com>
Date:	Thu, 17 Jul 2014 17:31:14 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Arnaldo Carvalho de Melo <acme@...nel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Paul Mackerras <paulus@...ba.org>,
	Namhyung Kim <namhyung.kim@....com>,
	LKML <linux-kernel@...r.kernel.org>,
	Jiri Olsa <jolsa@...hat.com>, Minchan Kim <minchan@...nel.org>
Subject: Re: [PATCH] perf stat: Pass PERF_STAT_RUN environment variable for
 each run

Hi Peter,

On Thu, Jul 17, 2014 at 5:26 PM, Peter Zijlstra <peterz@...radead.org> 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. :)

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/