From: Oliver Upton <oliver.upton@linux.dev>
To: Jinqian Yang <yangjinqian1@huawei.com>
Cc: yuzenghui@huawei.com, maz@kernel.org,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, liuyonglong@huawei.com,
wangzhou1@hisilicon.com
Subject: Re: [PATCH v2 1/3] KVM: arm64: Make ID_AA64MMFR1_EL1.HCX writable from userspace
Date: Tue, 9 Sep 2025 00:07:15 -0700 [thread overview]
Message-ID: <aL_SIwQiz3QO1fKe@linux.dev> (raw)
In-Reply-To: <20250909034415.3822478-2-yangjinqian1@huawei.com>
On Tue, Sep 09, 2025 at 11:44:13AM +0800, Jinqian Yang wrote:
> Allow userspace to downgrade HCX in ID_AA64MMFR1_EL1. Userspace can
> only change this value from high to low.
>
> Signed-off-by: Jinqian Yang <yangjinqian1@huawei.com>
I'm not sure our quality of emulation is that great in this case. We
have no way of trapping the register and it is always stateful. Better
yet, our RESx infrastructure doesn't account for the presence of
FEAT_HCX and we happily merge the contents with the host's HCRX.
We should make a reasonable attempt at upholding the architecture before
allowing userspace to de-feature FEAT_HCX.
Thanks,
Oliver
next prev parent reply other threads:[~2025-09-09 8:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 3:44 [PATCH v2 0/3] KVM: arm64: make EL2 feature fields writable in ID_AA64MMFR1_EL1 Jinqian Yang
2025-09-09 3:44 ` [PATCH v2 1/3] KVM: arm64: Make ID_AA64MMFR1_EL1.HCX writable from userspace Jinqian Yang
2025-09-09 7:07 ` Oliver Upton [this message]
2025-09-09 10:10 ` Marc Zyngier
2025-09-09 21:38 ` Oliver Upton
2025-09-10 1:57 ` Jinqian Yang
2025-09-09 3:44 ` [PATCH v2 2/3] KVM: arm64: Make ID_AA64MMFR1_EL1.TWED " Jinqian Yang
2025-09-09 3:44 ` [PATCH v2 3/3] KVM: arm64: Make ID_AA64MMFR1_EL1.VH " Jinqian Yang
2025-09-09 5:32 ` Oliver Upton
2025-09-10 1:42 ` Jinqian Yang
2025-09-09 7:00 ` [PATCH v2 0/3] KVM: arm64: make EL2 feature fields writable in ID_AA64MMFR1_EL1 Oliver Upton
2025-09-10 1:42 ` 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=aL_SIwQiz3QO1fKe@linux.dev \
--to=oliver.upton@linux.dev \
--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=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