linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manuel Selva <selva.manuel@gmail.com>
To: Andi Kleen <andi@firstfloor.org>, Harald Servat <harald.servat@bsc.es>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Sample memory references with at least a given latency?
Date: Thu, 05 Feb 2015 19:54:13 +0100	[thread overview]
Message-ID: <54D3BC55.1050302@gmail.com> (raw)
In-Reply-To: <87bnl8jnwf.fsf@tassilo.jf.intel.com>

What information is present in the samples recorded by perf record (on 
which ocperf relies) ?

Manu

On 02/05/2015 05:58 PM, Andi Kleen wrote:
> Harald Servat <harald.servat@bsc.es> writes:
>
>>    is there any way to configure perf to sample memory references
>> through PEBS and enable the Load Latency Performance Monitoring
>> Facility (section 18.7.1.2 from the Intel 64 and IA-32 Architectures
>> Software Developer's Manual).
>
> $ ocperf.py record -e mem_trans_retired.load_latency_gt_128 -a sleep 1
> perf record -e
> cpu/event=0xcd,umask=0x1,ldlat=0x80,name=mem_trans_retired_load_latency_gt_128/
> -a sleep 1
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.438 MB perf.data (~19125 samples) ]
>

  reply	other threads:[~2015-02-05 18:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 12:48 Sample memory references with at least a given latency? Harald Servat
     [not found] ` <CALbiyZyJhUNfMNOYwJ26P-Lq+3E_xM8SpZ9CG+WR70-n_k9x8A@mail.gmail.com>
2015-02-04 14:20   ` Harald Servat
2015-02-04 14:33     ` Vince Weaver
2015-02-05 11:33     ` Manuel Selva
2015-02-05 11:39       ` Harald Servat
2015-02-05 16:58 ` Andi Kleen
2015-02-05 18:54   ` Manuel Selva [this message]
2015-02-05 18:59     ` Andi Kleen
     [not found] ` <CALbiyZw=SqhFLtzse53SW_B-JMo-+AxPGDAE9C_aBmo4X88mrA@mail.gmail.com>
2015-02-04 13:34   ` Harald Servat
2015-02-18  9:31   ` Harald Servat

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=54D3BC55.1050302@gmail.com \
    --to=selva.manuel@gmail.com \
    --cc=andi@firstfloor.org \
    --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).