From: Oliver Upton <oliver.upton@linux.dev>
To: Jinqian Yang <yangjinqian1@huawei.com>
Cc: maz@kernel.org, yuzenghui@huawei.com,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, wangzhou1@hisilicon.com,
shameerali.kolothum.thodi@huawei.com, liuyonglong@huawei.com,
jiangkunkun@huawei.com
Subject: Re: [PATCH] KVM: arm64: Make HCX writable from userspace
Date: Tue, 25 Mar 2025 09:20:52 -0700 [thread overview]
Message-ID: <Z-LX5H5mjGyTQ9N4@linux.dev> (raw)
In-Reply-To: <20250325121126.1380681-1-yangjinqian1@huawei.com>
Hi Jinqian,
On Tue, Mar 25, 2025 at 08:11:26PM +0800, Jinqian Yang wrote:
> Allow userspace to modify guest visible value for HCX in
> ID_AA64MMFR1_EL1.
>
> Signed-off-by: Jinqian Yang <yangjinqian1@huawei.com>
This is fine, but I would rather we handle all the features like FEAT_HCX
instead of a trickle of one-off patches.
So, could you please:
- Identify all of the features that describe an *EL2* feature which
we've exposed to non-nested VMs
- Implement patch(es) to make those fields writable (i.e. allow them to
be downgraded)
- Add corresponding test cases to the set_id_regs selftest
Thanks,
Oliver
> ---
> arch/arm64/kvm/sys_regs.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c
> index 82430c1e1dd0..b105f156bdf6 100644
> --- a/arch/arm64/kvm/sys_regs.c
> +++ b/arch/arm64/kvm/sys_regs.c
> @@ -2666,7 +2666,6 @@ static const struct sys_reg_desc sys_reg_descs[] = {
> ID_AA64MMFR0_EL1_TGRAN16_2 |
> ID_AA64MMFR0_EL1_ASIDBITS)),
> ID_WRITABLE(ID_AA64MMFR1_EL1, ~(ID_AA64MMFR1_EL1_RES0 |
> - ID_AA64MMFR1_EL1_HCX |
> ID_AA64MMFR1_EL1_TWED |
> ID_AA64MMFR1_EL1_XNX |
> ID_AA64MMFR1_EL1_VH |
> --
> 2.33.0
>
next prev parent reply other threads:[~2025-03-25 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 12:11 [PATCH] KVM: arm64: Make HCX writable from userspace Jinqian Yang
2025-03-25 16:20 ` Oliver Upton [this message]
2025-05-27 13:05 ` Jinqian Yang
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=Z-LX5H5mjGyTQ9N4@linux.dev \
--to=oliver.upton@linux.dev \
--cc=jiangkunkun@huawei.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=maz@kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=yangjinqian1@huawei.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).