From: Andi Kleen <andi@firstfloor.org>
To: Omar Awile <omar.awile@cern.ch>
Cc: "linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
Aram Santogidis <aram.santogidis@cern.ch>,
kan.liang@intel.com
Subject: Re: perf record and intel_cqm/llc_occupancy
Date: Fri, 24 Jun 2016 09:43:50 -0700 [thread overview]
Message-ID: <20160624164350.GZ13997@two.firstfloor.org> (raw)
In-Reply-To: <etPan.576d272f.5dac2143.108@cern.ch>
On Fri, Jun 24, 2016 at 12:27:27PM +0000, Omar Awile wrote:
> 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?
perf stat cannot collect call graphs.
>
> 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?
perf can collect counts while sampling another event (called leader
sampling using :S). Unfortunately this does not work with events from
different PMUs, which would be needed here. Kan looked into this
some time ago, but there were too many problems with it.
>
> Finally, if none of the two alternatives work, do you have an idea how else this could be achieved?
For now the only way would be to sample and perf stat record in parallel
and then merge the data based on the time stamps. It likely will not
be very accurate.
-Andi
prev parent reply other threads:[~2016-06-24 16:43 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
2016-06-24 16:43 ` Andi Kleen [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=20160624164350.GZ13997@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=aram.santogidis@cern.ch \
--cc=kan.liang@intel.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=omar.awile@cern.ch \
/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).