From: Will Deacon <will@kernel.org>
To: Jing Zhang <jingzhangos@google.com>
Cc: maz@kernel.org, james.morse@arm.com,
julien.thierry.kdev@gmail.com, suzuki.poulose@arm.com,
catalin.marinas@arm.com, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org, qperret@google.com
Subject: Re: [PATCH] KVM: arm64: Remove redundant check for S2FWB
Date: Mon, 8 Mar 2021 16:49:02 +0000 [thread overview]
Message-ID: <20210308164902.GA26772@willie-the-truck> (raw)
In-Reply-To: <20210205044403.1559010-1-jingzhangos@google.com>
On Fri, Feb 05, 2021 at 04:44:03AM +0000, Jing Zhang wrote:
> Remove redundant check for CPU feature S2FWB in dcache flush code
> to save some CPU cycles for every memslot flush and unmapping.
> And move the S2FWB check to outer functions to avoid future
> redundancy and keep consistent with other usage like in
> access_dcsw and kvm_arch_prepare_memory_region.
>
> Signed-off-by: Jing Zhang <jingzhangos@google.com>
> ---
> arch/arm64/kvm/hyp/pgtable.c | 9 ++-------
> arch/arm64/kvm/mmu.c | 3 ++-
> 2 files changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/arch/arm64/kvm/hyp/pgtable.c b/arch/arm64/kvm/hyp/pgtable.c
> index bdf8e55ed308..afd57564b1cb 100644
> --- a/arch/arm64/kvm/hyp/pgtable.c
> +++ b/arch/arm64/kvm/hyp/pgtable.c
> @@ -642,9 +642,6 @@ int kvm_pgtable_stage2_map(struct kvm_pgtable *pgt, u64 addr, u64 size,
>
> static void stage2_flush_dcache(void *addr, u64 size)
> {
> - if (cpus_have_const_cap(ARM64_HAS_STAGE2_FWB))
> - return;
> -
> __flush_dcache_area(addr, size);
> }
>
> @@ -670,7 +667,8 @@ static int stage2_unmap_walker(u64 addr, u64 end, u32 level, kvm_pte_t *ptep,
>
> if (page_count(virt_to_page(childp)) != 1)
> return 0;
> - } else if (stage2_pte_cacheable(pte)) {
> + } else if (stage2_pte_cacheable(pte) &&
> + !cpus_have_const_cap(ARM64_HAS_STAGE2_FWB)) {
> need_flush = true;
> }
>
> @@ -846,9 +844,6 @@ int kvm_pgtable_stage2_flush(struct kvm_pgtable *pgt, u64 addr, u64 size)
> .flags = KVM_PGTABLE_WALK_LEAF,
> };
>
> - if (cpus_have_const_cap(ARM64_HAS_STAGE2_FWB))
> - return 0;
> -
> return kvm_pgtable_walk(pgt, addr, size, &walker);
> }
I think we should leave pgtable.c as it is: there's no benefit from this
change on the unmap path, and the other path involves the case where the
caller has asked for a flush and we can elide it.
> diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c
> index 7d2257cc5438..53130ed23304 100644
> --- a/arch/arm64/kvm/mmu.c
> +++ b/arch/arm64/kvm/mmu.c
> @@ -1458,7 +1458,8 @@ void kvm_toggle_cache(struct kvm_vcpu *vcpu, bool was_enabled)
> * If switching it off, need to clean the caches.
> * Clean + invalidate does the trick always.
> */
> - if (now_enabled != was_enabled)
> + if (now_enabled != was_enabled &&
> + !cpus_have_const_cap(ARM64_HAS_STAGE2_FWB))
> stage2_flush_vm(vcpu->kvm);
This change looks fine, but I don't grok the justification in your follow-up
email. You say:
| The saving is from the code path of memslot flush. The S2FWB check was
| in stage2_flush_dcache, in which case, for a memslot flush, the check
| was done for every page.
but I don't see where this is called for every page. It looks to me like it's
called for every pgd in the range, which is a very different kettle of frogs.
What am I missing?
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-08 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 4:44 [PATCH] KVM: arm64: Remove redundant check for S2FWB Jing Zhang
2021-02-05 17:24 ` Marc Zyngier
2021-02-05 18:56 ` Jing Zhang
2021-03-08 16:49 ` Will Deacon [this message]
2021-03-08 18:43 ` Jing Zhang
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=20210308164902.GA26772@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=jingzhangos@google.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=qperret@google.com \
--cc=suzuki.poulose@arm.com \
/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