linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Harald Servat <harald.servat@bsc.es>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Latency = weigth in perf mem record/report?
Date: Mon, 17 Feb 2014 17:02:30 +0100	[thread overview]
Message-ID: <20140217160230.GD3113@krava.brq.redhat.com> (raw)
In-Reply-To: <52FCFC1B.1000703@bsc.es>

On Thu, Feb 13, 2014 at 06:08:43PM +0100, Harald Servat wrote:
> Dear list,
> 
>   table 18-18 from the Vol 3b part 2 of the Intel® 64 and IA-32
> Architectures  Software Developer’s Manual (labeled as Table 18-18.
> PEBS Record Format for Intel Core i7 Processor Family ) [1]
> indicates that the PEBS samples report the latency value (in core
> cycles) for that particular load/store that emitted the sample at
> the address 0xa8 from the begin of the PEBS sample address.
> 
>   I've seen that there is a weight field in the output of the perf
> report -D associated to the PERF_RECORD_SAMPLE. Looking at the
> kernel code I found in file
> arch/x86/kernel/cpu/perf_event_intel_ds.c the following code which
> seems to be storing the info I want
> 
>  819         /*
>  820          * Use latency for weight (only avail with PEBS-LL)
>  821          */
>  822         if (fll && (sample_type & PERF_SAMPLE_WEIGHT))
>  823             data.weight = pebs->lat;
> 
>   and then in tools/perf/builtin-mem.c the routine dump_raw_samples
> seems to dump this info. Am I right? Can anyone kindly confirm this?

Right, PEBS latency info is stored in sample's WEIGHT (for mem-loads and
mem-stores events), and it's sample->weight on the perf tool side.

jirka

      reply	other threads:[~2014-02-17 16:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13 17:08 Latency = weigth in perf mem record/report? Harald Servat
2014-02-17 16:02 ` Jiri Olsa [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=20140217160230.GD3113@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=harald.servat@bsc.es \
    --cc=linux-perf-users@vger.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;
as well as URLs for NNTP newsgroup(s).