public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Stephane Eranian <eranian@google.com>,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 03/15] perf mem: Add -l/--ldlat option
Date: Wed, 24 Feb 2016 20:16:23 +0100	[thread overview]
Message-ID: <20160224191623.GA24004@krava.redhat.com> (raw)
In-Reply-To: <20160224131427.GB24505@kernel.org>

On Wed, Feb 24, 2016 at 10:14:27AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Feb 24, 2016 at 09:46:44AM +0100, Jiri Olsa escreveu:
> > Adding -l/--ldlat option to specify desired latency
> > for loads event.
> > 
> > Specify 50 as loads event latency:
> > 
> >   $ perf mem record -e ldlat-loads -v -l 50 true
> >   calling: record -W -d -e cpu/mem-loads,ldlat=50/P true
> 
> Please update the docs, also I think it is ok to leave it just as
> --ldlat, not using the one letter -l, we can do that if this becomes
> that frequently used.

ook, will do

thanks,
jirka

  reply	other threads:[~2016-02-24 19:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  8:46 [PATCHv2 00/15] perf tools: Several memory events updates Jiri Olsa
2016-02-24  8:46 ` [PATCH 01/15] perf mem: Check for memory events support Jiri Olsa
2016-02-25  7:36   ` [tip:perf/core] perf mem record: " tip-bot for Jiri Olsa
2016-02-24  8:46 ` [PATCH 02/15] perf mem: Introduce perf_mem_events__name function Jiri Olsa
2016-02-25  7:36   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-02-24  8:46 ` [PATCH 03/15] perf mem: Add -l/--ldlat option Jiri Olsa
2016-02-24 13:14   ` Arnaldo Carvalho de Melo
2016-02-24 19:16     ` Jiri Olsa [this message]
2016-02-24  8:46 ` [PATCH 04/15] perf mem: Add -u/-k options Jiri Olsa
2016-02-24 13:17   ` Arnaldo Carvalho de Melo
2016-02-24 19:17     ` Jiri Olsa
2016-02-24  8:46 ` [PATCH 05/15] perf tools: Introduce perf_mem__tlb_scnprintf function Jiri Olsa
2016-02-24 13:18   ` Arnaldo Carvalho de Melo
2016-02-25  7:37   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-02-24  8:46 ` [PATCH 06/15] perf tools: Introduce perf_mem__lvl_scnprintf function Jiri Olsa
2016-02-25  7:37   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-02-24  8:46 ` [PATCH 07/15] perf tools: Introduce perf_mem__snp_scnprintf function Jiri Olsa
2016-02-25  7:37   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-02-24  8:46 ` [PATCH 08/15] perf tools: Introduce perf_mem__lck_scnprintf function Jiri Olsa
2016-02-25  7:38   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-02-24  8:46 ` [PATCH 09/15] perf tools: Change perf_mem__tlb_scnprintf to return nb of displayed bytes Jiri Olsa
2016-02-25  7:38   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-02-24  8:46 ` [PATCH 10/15] perf tools: Change perf_mem__lvl_scnprintf " Jiri Olsa
2016-02-25  7:38   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-02-24  8:46 ` [PATCH 11/15] perf tools: Change perf_mem__snp_scnprintf " Jiri Olsa
2016-02-25  7:39   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-02-24  8:46 ` [PATCH 12/15] perf tools: Change perf_mem__lck_scnprintf " Jiri Olsa
2016-02-25  7:39   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-02-24  8:46 ` [PATCH 13/15] perf script: Display data_src values Jiri Olsa
2016-02-24 13:34   ` Arnaldo Carvalho de Melo
2016-02-24 19:18     ` Jiri Olsa
2016-02-25  7:39   ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-02-24  8:46 ` [PATCH 14/15] perf x86 intel: Add DATALA events into sysfs Jiri Olsa
2016-02-24 15:59   ` Andi Kleen
2016-02-24 18:54     ` Jiri Olsa
2016-02-24  8:46 ` [PATCH 15/15] perf mem: Add Intel DATALA memory events Jiri Olsa

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=20160224191623.GA24004@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox