linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "Andi Kleen" <andi@firstfloor.org>,
	"Vince Weaver" <vincent.weaver@maine.edu>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Jan Pokorný" <poki@redhat.com>,
	linux-perf-users@vger.kernel.org
Subject: Re: perf utility question: "Sky high iTLB-load-misses"
Date: Thu, 9 Nov 2017 06:38:38 -0800	[thread overview]
Message-ID: <20171109143838.GY2482@two.firstfloor.org> (raw)
In-Reply-To: <20171109135325.GJ4333@kernel.org>

On Thu, Nov 09, 2017 at 10:53:25AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Nov 08, 2017 at 11:55:02AM -0500, Vince Weaver escreveu:
> > On Wed, 8 Nov 2017, Jan Pokorný wrote:
> > 
> > > Is iTLB-load-misses > 100% reported because of some deficiency
> > > of the platform, a bug in perf, or an expected behaviour?
> > 
> > If you look into the kernel, the two events being measured are
> > 	[ C(RESULT_ACCESS) ] = 0x2085,  /* ITLB_MISSES.STLB_HIT */
> > 	[ C(RESULT_MISS)   ] = 0xe85,   /* ITLB_MISSES.WALK_COMPLETED */
> > 
> > If you look this up in Intel Vol3b you can see that the "access" metric
> > measures First level ITLB misses that hit in the Second-level TLB
> > 
> > Wheras the miss metric is a list of accesses from any level that caused a 
> > walk of the page tables.
> > 
> > So the events don't necessarily sound like they match up very well, so 
> > it's beleivable you will get odd results when trying to calculate 
> > percentages based on them.
> 
> Andi, is this something you can help in figuring out a fix? Peter?

See "perf list itlb"

itlb access could be replaced with instructions retired,
but I suspect that is also not what you're looking for.

Only other alternative would be to disable the events.

-Andi

  reply	other threads:[~2017-11-09 14:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 16:34 perf utility question: "Sky high iTLB-load-misses" Jan Pokorný
2017-11-08 16:55 ` Vince Weaver
2017-11-09 13:53   ` Arnaldo Carvalho de Melo
2017-11-09 14:38     ` Andi Kleen [this message]
2017-11-09 18:50       ` Jan Pokorný
2017-11-09 19:12         ` Bram Stolk
2017-11-09 19:37           ` Vince Weaver

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=20171109143838.GY2482@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=acme@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=poki@redhat.com \
    --cc=vincent.weaver@maine.edu \
    /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).