From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>, James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
Reiji Watanabe <reijiw@google.com>,
Andrew Jones <andrew.jones@linux.dev>,
Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH v3 0/7] KVM: arm64: Use visibility hook to treat ID regs as RAZ
Date: Tue, 13 Sep 2022 09:44:33 +0000 [thread overview]
Message-ID: <20220913094441.3957645-1-oliver.upton@linux.dev> (raw)
For reasons unknown, the Arm architecture defines the 64-bit views of
the 32-bit ID registers as UNKNOWN [1]. This combines poorly with the
fact that KVM unconditionally exposes these registers to userspace,
which could throw a wrench in migration between 64-bit only systems.
This series reworks KVM's definition of these registers to RAZ/WI with
the goal of providing consistent register values across 64-bit machines.
Patches 1-3 clean up the ID register accessors, taking advantage of the
fact that the generic accessors know how to handle RAZ.
Patches 4-6 start switch the handling of potentially nonzero AArch32 ID
registers to RAZ/WI. RAZ covers up the architecturally UNKNOWN values,
and WI allows for migration off of kernels that may provide garbage.
Note that hidden AArch32 ID registers continue to have RAZ behavior with
the additional expectation of invariance.
Lastly, patch 7 includes a small test for the issue.
Applies to 6.0-rc3. Tested with KVM selftests under the fast model w/
asymmetric 32 bit support and no 32 bit support whatsoever.
[1]: DDI0487H.a Table D12-2 'Instruction encodings for non-Debug System Register accesses'
v2: https://lore.kernel.org/kvmarm/20220902154804.1939819-1-oliver.upton@linux.dev/
v2 -> v3:
- Collect more of Reiji's r-bs (thanks again!)
- Test the RAZ+invariant registers (AFR0, DFR1, unallocated AA32 ID
registers) (Drew)
- Give the selftest a more sensible name
v1 -> v2:
- Collect Reiji's r-b tags (thanks!)
- Call sysreg_visible_as_raz() from read_id_reg() (Reiji)
- Hoist sysreg_user_write_ignore() into kvm_sys_reg_set_user() (Reiji)
Oliver Upton (7):
KVM: arm64: Use visibility hook to treat ID regs as RAZ
KVM: arm64: Remove internal accessor helpers for id regs
KVM: arm64: Drop raz parameter from read_id_reg()
KVM: arm64: Spin off helper for calling visibility hook
KVM: arm64: Add a visibility bit to ignore user writes
KVM: arm64: Treat 32bit ID registers as RAZ/WI on 64bit-only system
KVM: selftests: Add test for AArch32 ID registers
arch/arm64/kvm/sys_regs.c | 150 ++++++++--------
arch/arm64/kvm/sys_regs.h | 24 ++-
tools/testing/selftests/kvm/.gitignore | 1 +
tools/testing/selftests/kvm/Makefile | 1 +
.../selftests/kvm/aarch64/aarch32_id_regs.c | 169 ++++++++++++++++++
5 files changed, 259 insertions(+), 86 deletions(-)
create mode 100644 tools/testing/selftests/kvm/aarch64/aarch32_id_regs.c
base-commit: b90cb1053190353cc30f0fef0ef1f378ccc063c5
--
2.37.2.789.g6183377224-goog
next reply other threads:[~2022-09-13 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 9:44 Oliver Upton [this message]
2022-09-13 9:44 ` [PATCH v3 1/7] KVM: arm64: Use visibility hook to treat ID regs as RAZ Oliver Upton
2022-09-13 9:44 ` [PATCH v3 2/7] KVM: arm64: Remove internal accessor helpers for id regs Oliver Upton
2022-09-13 9:44 ` [PATCH v3 3/7] KVM: arm64: Drop raz parameter from read_id_reg() Oliver Upton
2022-09-13 9:44 ` [PATCH v3 4/7] KVM: arm64: Spin off helper for calling visibility hook Oliver Upton
2022-09-13 9:44 ` [PATCH v3 5/7] KVM: arm64: Add a visibility bit to ignore user writes Oliver Upton
2022-09-13 9:44 ` [PATCH v3 6/7] KVM: arm64: Treat 32bit ID registers as RAZ/WI on 64bit-only system Oliver Upton
2022-09-13 9:44 ` [PATCH v3 7/7] KVM: selftests: Add test for AArch32 ID registers Oliver Upton
2022-09-14 10:41 ` [PATCH v3 0/7] KVM: arm64: Use visibility hook to treat ID regs as RAZ 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=20220913094441.3957645-1-oliver.upton@linux.dev \
--to=oliver.upton@linux.dev \
--cc=alexandru.elisei@arm.com \
--cc=andrew.jones@linux.dev \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=reijiw@google.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