From: Joey Gouly <joey.gouly@arm.com>
To: Marc Zyngier <maz@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Zenghui Yu <yuzenghui@huawei.com>,
D Scott Phillips <scott@os.amperecomputing.com>
Subject: Re: [PATCH 2/3] KVM: arm64: Teach address translation about access faults
Date: Tue, 22 Apr 2025 14:50:08 +0100 [thread overview]
Message-ID: <20250422135008.GA747658@e124191.cambridge.arm.com> (raw)
In-Reply-To: <20250422122612.2675672-3-maz@kernel.org>
On Tue, Apr 22, 2025 at 01:26:11PM +0100, Marc Zyngier wrote:
> It appears that our S1 PTW is completely oblivious of access faults.
> Teach the S1 translation code about it.
>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> ---
> arch/arm64/kvm/at.c | 26 +++++++++++++++++++++-----
> 1 file changed, 21 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm64/kvm/at.c b/arch/arm64/kvm/at.c
> index 3a4568e2de910..c40583edebc4f 100644
> --- a/arch/arm64/kvm/at.c
> +++ b/arch/arm64/kvm/at.c
> @@ -456,6 +456,11 @@ static int walk_s1(struct kvm_vcpu *vcpu, struct s1_walk_info *wi,
> if (check_output_size(desc & GENMASK(47, va_bottom), wi))
> goto addrsz;
>
> + if (!(desc & PTE_AF)) {
> + fail_s1_walk(wr, ESR_ELx_FSC_ACCESS_L(level), false);
> + return -EACCES;
> + }
> +
> va_bottom += contiguous_bit_shift(desc, wi, level);
>
> wr->failed = false;
> @@ -1209,7 +1214,8 @@ static u64 handle_at_slow(struct kvm_vcpu *vcpu, u32 op, u64 vaddr)
> * If the translation is unsuccessful, the value may only contain
> * PAR_EL1.F, and cannot be taken at face value. It isn't an
> * indication of the translation having failed, only that the fast
> - * path did not succeed, *unless* it indicates a S1 permission fault.
> + * path did not succeed, *unless* it indicates a S1 permission or
> + * access fault.
> */
> static u64 __kvm_at_s1e01_fast(struct kvm_vcpu *vcpu, u32 op, u64 vaddr)
> {
> @@ -1312,19 +1318,29 @@ static bool par_check_s1_perm_fault(u64 par)
> !(par & SYS_PAR_EL1_S));
> }
>
> +static bool par_check_s1_access_fault(u64 par)
> +{
> + u8 fst = FIELD_GET(SYS_PAR_EL1_FST, par);
> +
> + return ((fst & ESR_ELx_FSC_TYPE) == ESR_ELx_FSC_ACCESS &&
> + !(par & SYS_PAR_EL1_S));
> +}
> +
> void __kvm_at_s1e01(struct kvm_vcpu *vcpu, u32 op, u64 vaddr)
> {
> u64 par = __kvm_at_s1e01_fast(vcpu, op, vaddr);
>
> /*
> - * If PAR_EL1 reports that AT failed on a S1 permission fault, we
> - * know for sure that the PTW was able to walk the S1 tables and
> - * there's nothing else to do.
> + * If PAR_EL1 reports that AT failed on a S1 permission or access
> + * fault, we know for sure that the PTW was able to walk the S1
> + * tables and there's nothing else to do.
> *
> * If AT failed for any other reason, then we must walk the guest S1
> * to emulate the instruction.
> */
> - if ((par & SYS_PAR_EL1_F) && !par_check_s1_perm_fault(par))
> + if ((par & SYS_PAR_EL1_F) &&
> + !par_check_s1_perm_fault(par) &&
> + !par_check_s1_access_fault(par))
> par = handle_at_slow(vcpu, op, vaddr);
>
> vcpu_write_sys_reg(vcpu, par, PAR_EL1);
Reviewed-by: Joey Gouly <joey.gouly@arm.com>
next prev parent reply other threads:[~2025-04-22 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 12:26 [PATCH 0/3] KVM: arm64: Address Translation fixes Marc Zyngier
2025-04-22 12:26 ` [PATCH 1/3] KVM: arm64: Fix PAR_EL1.{PTW,S} reporting on AT S1E* Marc Zyngier
2025-04-22 12:26 ` [PATCH 2/3] KVM: arm64: Teach address translation about access faults Marc Zyngier
2025-04-22 13:50 ` Joey Gouly [this message]
2025-04-22 20:54 ` D Scott Phillips
2025-04-22 21:19 ` Marc Zyngier
2025-04-22 12:26 ` [PATCH 3/3] KVM: arm64: Don't feed uninitialised data to HCR_EL2 Marc Zyngier
2025-05-14 9:47 ` [PATCH 0/3] KVM: arm64: Address Translation fixes Marc Zyngier
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=20250422135008.GA747658@e124191.cambridge.arm.com \
--to=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=scott@os.amperecomputing.com \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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;
as well as URLs for NNTP newsgroup(s).