From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>
Cc: kvmarm@lists.linux.dev, kvm@vger.kernel.org,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Jing Zhang <jingzhangos@google.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [PATCH v11 00/12] KVM: arm64: Enable 'writable' ID registers
Date: Wed, 4 Oct 2023 16:53:16 +0000 [thread overview]
Message-ID: <ZR2YfAixZgbCFnb8@linux.dev> (raw)
In-Reply-To: <86mswyohcy.wl-maz@kernel.org>
On Wed, Oct 04, 2023 at 10:40:45AM +0100, Marc Zyngier wrote:
> On Wed, 04 Oct 2023 00:03:56 +0100,
> Oliver Upton <oliver.upton@linux.dev> wrote:
> >
> > Few more fixes that I threw on top:
> >
> > v10 -> v11:
> > - Drop the custom handling of FEAT_BC as it is now fixed on the arm64
> > side (Kristina)
> > - Bikeshed on the naming of the masks ioctl to keep things in the KVM_
> > namespace
> > - Apply more bikeshedding to the ioctl documentation, spinning off
> > separate blocks for the 'generic' description and the Feature ID
> > documentation
> > - Fix referencing in the vCPU features doc
> > - Fix use of uninitialized data in selftest
>
> We'll probably need another bit on top to deal with Kirstina's
> FEAT_MOPS series and make that field writable.
Yep, I was planning on a one-liner to unmask MOPS once I get Kristina's
patches applied.
> The minor nitpicks I had notwithstanding:
>
> Reviewed-by: Marc Zyngier <maz@kernel.org>
Appreciated!
--
Thanks,
Oliver
next prev parent reply other threads:[~2023-10-04 16:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 23:03 [PATCH v11 00/12] KVM: arm64: Enable 'writable' ID registers Oliver Upton
2023-10-03 23:03 ` [PATCH v11 01/12] KVM: arm64: Allow userspace to get the writable masks for feature " Oliver Upton
2023-10-03 23:03 ` [PATCH v11 02/12] KVM: arm64: Document KVM_ARM_GET_REG_WRITABLE_MASKS Oliver Upton
2023-10-03 23:03 ` [PATCH v11 03/12] KVM: arm64: Use guest ID register values for the sake of emulation Oliver Upton
2023-10-03 23:04 ` [PATCH v11 04/12] KVM: arm64: Reject attempts to set invalid debug arch version Oliver Upton
2023-10-03 23:04 ` [PATCH v11 05/12] KVM: arm64: Bump up the default KVM sanitised debug version to v8p8 Oliver Upton
2023-10-04 8:57 ` Marc Zyngier
2023-10-04 17:08 ` Oliver Upton
2023-10-04 17:46 ` Marc Zyngier
2023-10-03 23:04 ` [PATCH v11 06/12] KVM: arm64: Allow userspace to change ID_AA64ISAR{0-2}_EL1 Oliver Upton
2023-10-03 23:04 ` [PATCH v11 07/12] KVM: arm64: Allow userspace to change ID_AA64MMFR{0-2}_EL1 Oliver Upton
2023-10-03 23:04 ` [PATCH v11 08/12] KVM: arm64: Allow userspace to change ID_AA64PFR0_EL1 Oliver Upton
2023-10-03 23:04 ` [PATCH v11 09/12] KVM: arm64: Allow userspace to change ID_AA64ZFR0_EL1 Oliver Upton
2023-10-03 23:04 ` [PATCH v11 10/12] KVM: arm64: Document vCPU feature selection UAPIs Oliver Upton
2023-10-04 9:36 ` Marc Zyngier
2023-10-04 16:52 ` Oliver Upton
2023-10-04 17:48 ` Marc Zyngier
2023-10-03 23:04 ` [PATCH v11 11/12] KVM: arm64: selftests: Import automatic generation of sysreg defs Oliver Upton
2023-10-03 23:04 ` [PATCH v11 12/12] KVM: arm64: selftests: Test for setting ID register from usersapce Oliver Upton
2023-10-04 9:40 ` [PATCH v11 00/12] KVM: arm64: Enable 'writable' ID registers Marc Zyngier
2023-10-04 16:53 ` Oliver Upton [this message]
2023-10-04 17:46 ` 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=ZR2YfAixZgbCFnb8@linux.dev \
--to=oliver.upton@linux.dev \
--cc=cohuck@redhat.com \
--cc=james.morse@arm.com \
--cc=jingzhangos@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--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