From: Quentin Perret <qperret@google.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Will Deacon <will@kernel.org>, Fuad Tabba <tabba@google.com>
Subject: Re: [PATCH] KVM: arm64: pkvm: Use the mm_ops indirection for cache maintenance
Date: Fri, 14 Jan 2022 13:49:12 +0000 [thread overview]
Message-ID: <YeF/WMXe4HL/n8qw@google.com> (raw)
In-Reply-To: <20220114125038.1336965-1-maz@kernel.org>
On Friday 14 Jan 2022 at 12:50:38 (+0000), Marc Zyngier wrote:
> CMOs issued from EL2 cannot directly use the kernel helpers,
> as EL2 doesn't have a mapping of the guest pages. Oops.
>
> Instead, use the mm_ops indirection to use helpers that will
> perform a mapping at EL2 and allow the CMO to be effective.
Right, we were clearly lucky not to use those paths at EL2 _yet_, but
that's going to change soon and this is better for consistency, so:
Reviewed-by: Quentin Perret <qperret@google.com>
> Fixes: 25aa28691bb9 ("KVM: arm64: Move guest CMOs to the fault handlers")
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> ---
> arch/arm64/kvm/hyp/pgtable.c | 18 ++++++------------
> 1 file changed, 6 insertions(+), 12 deletions(-)
>
> diff --git a/arch/arm64/kvm/hyp/pgtable.c b/arch/arm64/kvm/hyp/pgtable.c
> index 844a6f003fd5..2cb3867eb7c2 100644
> --- a/arch/arm64/kvm/hyp/pgtable.c
> +++ b/arch/arm64/kvm/hyp/pgtable.c
> @@ -983,13 +983,9 @@ static int stage2_unmap_walker(u64 addr, u64 end, u32 level, kvm_pte_t *ptep,
> */
> stage2_put_pte(ptep, mmu, addr, level, mm_ops);
>
> - if (need_flush) {
> - kvm_pte_t *pte_follow = kvm_pte_follow(pte, mm_ops);
> -
> - dcache_clean_inval_poc((unsigned long)pte_follow,
> - (unsigned long)pte_follow +
> - kvm_granule_size(level));
> - }
> + if (need_flush && mm_ops->dcache_clean_inval_poc)
> + mm_ops->dcache_clean_inval_poc(kvm_pte_follow(pte, mm_ops),
> + kvm_granule_size(level));
>
> if (childp)
> mm_ops->put_page(childp);
> @@ -1151,15 +1147,13 @@ static int stage2_flush_walker(u64 addr, u64 end, u32 level, kvm_pte_t *ptep,
> struct kvm_pgtable *pgt = arg;
> struct kvm_pgtable_mm_ops *mm_ops = pgt->mm_ops;
> kvm_pte_t pte = *ptep;
> - kvm_pte_t *pte_follow;
>
> if (!kvm_pte_valid(pte) || !stage2_pte_cacheable(pgt, pte))
> return 0;
>
> - pte_follow = kvm_pte_follow(pte, mm_ops);
> - dcache_clean_inval_poc((unsigned long)pte_follow,
> - (unsigned long)pte_follow +
> - kvm_granule_size(level));
> + if (mm_ops->dcache_clean_inval_poc)
> + mm_ops->dcache_clean_inval_poc(kvm_pte_follow(pte, mm_ops),
> + kvm_granule_size(level));
> return 0;
> }
>
> --
> 2.30.2
>
prev parent reply other threads:[~2022-01-14 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 12:50 [PATCH] KVM: arm64: pkvm: Use the mm_ops indirection for cache maintenance Marc Zyngier
2022-01-14 13:49 ` Quentin Perret [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=YeF/WMXe4HL/n8qw@google.com \
--to=qperret@google.com \
--cc=alexandru.elisei@arm.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=will@kernel.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).