linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Omar Awile <omar.awile@cern.ch>
To: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	Aram Santogidis <aram.santogidis@cern.ch>
Subject: Re: perf record and intel_cqm/llc_occupancy
Date: Fri, 24 Jun 2016 12:27:27 +0000	[thread overview]
Message-ID: <etPan.576d272f.5dac2143.108@cern.ch> (raw)
In-Reply-To: <8760szocdp.fsf@tassilo.jf.intel.com>

Hi Andi,

Thanks, I see your point. I’ve seen tried perf stat for these events, which is quite nice. However, we would like to be able to correlate the cache occupancy with the current call stack. I don’t see how this could be done with perf stat. Is there a way to do this?

Alternatively, since perf record already keeps track of the call stack, is it feasible to extend it to allow recording cache occupancy, or is this inherently impossible?

Finally, if none of the two alternatives work, do you have an idea how else this could be achieved?

Thanks!

Omar

PS. sorry for repost...

On 23 June 2016 at 22:53:43, Andi Kleen (andi@firstfloor.org(mailto:andi@firstfloor.org)) wrote:

> Omar Awile writes:
> >
> > Is it possible that for intel_cqm/llc_occupancy interrupts are not
> > supported?5A
>  
> Interrupts wouldn't be meaningful on these counters because they
> don't count continuous events, but just report the current cache
> occupancy. So yes.
>  
> You can use perf stat -I ... instead to get a time series.
>  
> -Andi

  reply	other threads:[~2016-06-24 12:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 15:42 perf record and intel_cqm/llc_occupancy Omar Awile
2016-06-23 20:53 ` Andi Kleen
2016-06-24 12:27   ` Omar Awile [this message]
2016-06-24 16:43     ` Andi Kleen

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=etPan.576d272f.5dac2143.108@cern.ch \
    --to=omar.awile@cern.ch \
    --cc=andi@firstfloor.org \
    --cc=aram.santogidis@cern.ch \
    --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).