From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 3/3] target/arm: Flush only the TLBs affected by TTBR*_EL1
Date: Fri, 19 Oct 2018 08:21:59 -0700 [thread overview]
Message-ID: <1dda484c-1fc8-f75e-3150-111b0c7d85f9@linaro.org> (raw)
In-Reply-To: <CAFEAcA81rDucGOEVYi1LCw=1eiHisuM8+yXGzaw2dMktdU99cw@mail.gmail.com>
On 10/19/18 7:28 AM, Peter Maydell wrote:
> On 19 October 2018 at 02:56, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>> Only the EL0 and EL1 TLBs are affected by the EL1 register,
>> so flush only 2 of the 8 TLBs.
>>
>> In testing a boot of the Ubuntu installer to the first menu, this
>> accounts for nearly all of the full tlb flushes: all but 11k of
>> the 1.2M instances without the patch.
>>
>> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
>> ---
>> target/arm/helper.c | 16 +++++++++-------
>> 1 file changed, 9 insertions(+), 7 deletions(-)
>>
>> diff --git a/target/arm/helper.c b/target/arm/helper.c
>> index ed70ac645e..3ba8e66487 100644
>> --- a/target/arm/helper.c
>> +++ b/target/arm/helper.c
>> @@ -2706,14 +2706,16 @@ static void vmsa_tcr_el1_write(CPUARMState *env, const ARMCPRegInfo *ri,
>> tcr->raw_tcr = value;
>> }
>>
>> -static void vmsa_ttbr_write(CPUARMState *env, const ARMCPRegInfo *ri,
>> - uint64_t value)
>> +static void vmsa_ttbr_el1_write(CPUARMState *env, const ARMCPRegInfo *ri,
>> + uint64_t value)
>> {
>> /* If the ASID changes (with a 64-bit write), we must flush the TLB. */
>> if (cpreg_field_is_64bit(ri) &&
>> extract64(raw_read(env, ri) ^ value, 48, 16) != 0) {
>> ARMCPU *cpu = arm_env_get_cpu(env);
>> - tlb_flush(CPU(cpu));
>> + tlb_flush_by_mmuidx(CPU(cpu),
>> + ARMMMUIdxBit_S12NSE1 |
>> + ARMMMUIdxBit_S12NSE0);
>
> This isn't taking account of the possibility of secure mode.
> ARMMMUIdxBit_S1SE0 and ARMMMUIdxBit_S1SE1 might also be affected.
Ah. Is there an easy way to tell if secure mode is present/enabled? It'd be
nice to not flush tlbs that aren't in use...
> And for AArch32, this writefn is used for the secure-banked versions
> of TTBR0/TTBR1, which means ARMMMUIdxBit_S1E3 may also need flushing.
For aarch32, we don't have an asid, and so do not flush at all.
r~
next prev parent reply other threads:[~2018-10-19 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 1:56 [Qemu-devel] [PATCH v2 0/3] target/arm: Reduce tlb_flush overhead Richard Henderson
2018-10-19 1:56 ` [Qemu-devel] [PATCH v2 1/3] target/arm: Remove writefn from TTBR0_EL3 Richard Henderson
2018-10-19 14:22 ` Peter Maydell
2018-10-19 1:56 ` [Qemu-devel] [PATCH v2 2/3] target/arm: Only flush tlb if ASID changes Richard Henderson
2018-10-19 5:00 ` Philippe Mathieu-Daudé
2018-10-19 14:22 ` Peter Maydell
2018-10-19 1:56 ` [Qemu-devel] [PATCH v2 3/3] target/arm: Flush only the TLBs affected by TTBR*_EL1 Richard Henderson
2018-10-19 14:28 ` Peter Maydell
2018-10-19 15:21 ` Richard Henderson [this message]
2018-10-19 16:12 ` Peter Maydell
2018-10-19 16:31 ` Richard Henderson
2018-10-19 16:37 ` Peter Maydell
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=1dda484c-1fc8-f75e-3150-111b0c7d85f9@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).