From: Mario Smarduch <m.smarduch@samsung.com>
To: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Marc Zyngier <Marc.Zyngier@arm.com>,
"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>
Subject: tlbi va, vaa vs. val, vaal
Date: Thu, 26 Feb 2015 16:12:32 -0800 [thread overview]
Message-ID: <54EFB670.2070501@samsung.com> (raw)
I noticed kernel tlbflush.h use tlbi va*, vaa* variants instead of
val, vaal ones. Reading the manual D.5.7.2 it appears that
va*, vaa* versions invalidate intermediate caching of
translation structures.
With stage2 enabled that may result in 20+ memory lookups
for a 4 level page table walk. That's assuming that intermediate
caching structures cache mappings from stage1 table entry to
host page.
- Mario
WARNING: multiple messages have this Message-ID (diff)
From: m.smarduch@samsung.com (Mario Smarduch)
To: linux-arm-kernel@lists.infradead.org
Subject: tlbi va, vaa vs. val, vaal
Date: Thu, 26 Feb 2015 16:12:32 -0800 [thread overview]
Message-ID: <54EFB670.2070501@samsung.com> (raw)
I noticed kernel tlbflush.h use tlbi va*, vaa* variants instead of
val, vaal ones. Reading the manual D.5.7.2 it appears that
va*, vaa* versions invalidate intermediate caching of
translation structures.
With stage2 enabled that may result in 20+ memory lookups
for a 4 level page table walk. That's assuming that intermediate
caching structures cache mappings from stage1 table entry to
host page.
- Mario
next reply other threads:[~2015-02-27 0:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 0:12 Mario Smarduch [this message]
2015-02-27 0:12 ` tlbi va, vaa vs. val, vaal Mario Smarduch
2015-02-27 10:24 ` Will Deacon
2015-02-27 10:24 ` Will Deacon
2015-02-27 10:29 ` Marc Zyngier
2015-02-27 10:29 ` Marc Zyngier
2015-02-27 10:33 ` Will Deacon
2015-02-27 10:33 ` Will Deacon
2015-02-27 10:44 ` Marc Zyngier
2015-02-27 10:44 ` Marc Zyngier
2015-02-27 21:15 ` Mario Smarduch
2015-02-27 21:15 ` Mario Smarduch
2015-03-02 16:23 ` Catalin Marinas
2015-03-02 16:23 ` Catalin Marinas
2015-03-02 19:26 ` Mario Smarduch
2015-03-02 19:26 ` Mario Smarduch
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=54EFB670.2070501@samsung.com \
--to=m.smarduch@samsung.com \
--cc=Marc.Zyngier@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.