All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
	Namhyung Kim <namhyung.kim@lge.com>,
	LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
	Minchan Kim <minchan@kernel.org>
Subject: Re: [PATCH] perf stat: Pass PERF_STAT_RUN environment variable for each run
Date: Fri, 18 Jul 2014 14:06:08 +0900	[thread overview]
Message-ID: <87d2d3l0hr.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20140717130943.GA4312@kernel.org> (Arnaldo Carvalho de Melo's message of "Thu, 17 Jul 2014 10:09:43 -0300")

Hi Arnaldo and Peter,

On Thu, 17 Jul 2014 10:09:43 -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Jul 17, 2014 at 10:40:11AM +0200, Peter Zijlstra escreveu:
>> On Thu, Jul 17, 2014 at 05:31:14PM +0900, Namhyung Kim wrote:
>> > On Thu, Jul 17, 2014 at 5:26 PM, Peter Zijlstra <peterz@infradead.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. :)
>
>> 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.
>
> Agreed, one can script this using --pre or --post if needed.

Hmm... okay, I'll drop this then.

Thanks,
Namhyung

      reply	other threads:[~2014-07-18  5:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17  8:21 [PATCH] perf stat: Pass PERF_STAT_RUN environment variable for each run Namhyung Kim
2014-07-17  8:26 ` Peter Zijlstra
2014-07-17  8:31   ` Namhyung Kim
2014-07-17  8:40     ` Peter Zijlstra
2014-07-17 13:09       ` Arnaldo Carvalho de Melo
2014-07-18  5:06         ` Namhyung Kim [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d2d3l0hr.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.