From: Oliver Upton <oliver.upton@linux.dev>
To: Sebastian Ott <sebott@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: arm64: Writable TGRAN*_2
Date: Wed, 12 Mar 2025 10:20:03 -0700 [thread overview]
Message-ID: <Z9HCQ40LxShzL4nj@linux.dev> (raw)
In-Reply-To: <20250306184013.30008-1-sebott@redhat.com>
Hi Sebastian,
On Thu, Mar 06, 2025 at 07:40:13PM +0100, Sebastian Ott wrote:
> Allow userspace to write the safe (NI) value for ID_AA64MMFR0_EL1.TGRAN*_2.
> Disallow to change these fields for NV since kvm provides a sanitized view
> for them based on the PAGE_SIZE.
> Also add these bits to the set_id_regs selftest.
>
> Signed-off-by: Sebastian Ott <sebott@redhat.com>
I can't tell what you've based this patch on, it certainly doesn't apply
on a 6.14 rc. Consider telling git to include the base commit next time
you generate a patch.
> ---
> arch/arm64/kvm/sys_regs.c | 21 +++++++++++++++----
> .../testing/selftests/kvm/arm64/set_id_regs.c | 3 +++
> 2 files changed, 20 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c
> index 14faf213d483..0730ed8314d0 100644
> --- a/arch/arm64/kvm/sys_regs.c
> +++ b/arch/arm64/kvm/sys_regs.c
> @@ -1948,6 +1948,21 @@ static int set_id_aa64pfr1_el1(struct kvm_vcpu *vcpu,
> return set_id_reg(vcpu, rd, user_val);
> }
>
> +static int set_id_aa64mmfr0_el1(struct kvm_vcpu *vcpu,
> + const struct sys_reg_desc *rd, u64 user_val)
> +{
> + u64 sanitized_val = kvm_read_sanitised_id_reg(vcpu, rd);
> + u64 tgran2_mask = ID_AA64MMFR0_EL1_TGRAN4_2_MASK |
> + ID_AA64MMFR0_EL1_TGRAN16_2_MASK |
> + ID_AA64MMFR0_EL1_TGRAN64_2_MASK;
> +
> + if (vcpu_has_nv(vcpu) &&
> + ((sanitized_val & tgran2_mask) != (user_val & tgran2_mask)))
> + return -EINVAL;
> +
> + return set_id_reg(vcpu, rd, user_val);
> +}
> +
> static int set_id_aa64mmfr2_el1(struct kvm_vcpu *vcpu,
> const struct sys_reg_desc *rd, u64 user_val)
> {
> @@ -2787,10 +2802,8 @@ static const struct sys_reg_desc sys_reg_descs[] = {
> ID_UNALLOCATED(6,7),
>
> /* CRm=7 */
> - ID_WRITABLE(ID_AA64MMFR0_EL1, ~(ID_AA64MMFR0_EL1_RES0 |
> - ID_AA64MMFR0_EL1_TGRAN4_2 |
> - ID_AA64MMFR0_EL1_TGRAN64_2 |
> - ID_AA64MMFR0_EL1_TGRAN16_2 |
> + ID_FILTERED(ID_AA64MMFR0_EL1, id_aa64mmfr0_el1,
> + ~(ID_AA64MMFR0_EL1_RES0 |
> ID_AA64MMFR0_EL1_ASIDBITS)),
> ID_WRITABLE(ID_AA64MMFR1_EL1, ~(ID_AA64MMFR1_EL1_RES0 |
> ID_AA64MMFR1_EL1_HCX |
> diff --git a/tools/testing/selftests/kvm/arm64/set_id_regs.c b/tools/testing/selftests/kvm/arm64/set_id_regs.c
> index 1d65f4a09e6f..322b9d3b0125 100644
> --- a/tools/testing/selftests/kvm/arm64/set_id_regs.c
> +++ b/tools/testing/selftests/kvm/arm64/set_id_regs.c
> @@ -146,6 +146,9 @@ static const struct reg_ftr_bits ftr_id_aa64pfr1_el1[] = {
> static const struct reg_ftr_bits ftr_id_aa64mmfr0_el1[] = {
> REG_FTR_BITS(FTR_LOWER_SAFE, ID_AA64MMFR0_EL1, ECV, 0),
> REG_FTR_BITS(FTR_LOWER_SAFE, ID_AA64MMFR0_EL1, EXS, 0),
> + REG_FTR_BITS(FTR_EXACT, ID_AA64MMFR0_EL1, TGRAN4_2, 1),
> + REG_FTR_BITS(FTR_EXACT, ID_AA64MMFR0_EL1, TGRAN64_2, 1),
> + REG_FTR_BITS(FTR_EXACT, ID_AA64MMFR0_EL1, TGRAN16_2, 1),
> S_REG_FTR_BITS(FTR_LOWER_SAFE, ID_AA64MMFR0_EL1, TGRAN4, 0),
> S_REG_FTR_BITS(FTR_LOWER_SAFE, ID_AA64MMFR0_EL1, TGRAN64, 0),
> REG_FTR_BITS(FTR_LOWER_SAFE, ID_AA64MMFR0_EL1, TGRAN16, 0),
Please do selftests changes in a separate patch.
Don't worry about respinning, I'll fix this up and queue it in a moment.
Thanks,
Oliver
next prev parent reply other threads:[~2025-03-12 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 18:40 [PATCH] KVM: arm64: Writable TGRAN*_2 Sebastian Ott
2025-03-09 18:24 ` Marc Zyngier
2025-03-12 17:20 ` Oliver Upton [this message]
2025-03-12 17:32 ` Oliver Upton
2025-03-12 17:33 ` Sebastian Ott
2025-03-12 21:04 ` Oliver Upton
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=Z9HCQ40LxShzL4nj@linux.dev \
--to=oliver.upton@linux.dev \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=sebott@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--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 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.