public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Alexandru Elisei <alexandru.elisei@arm.com>,
	Oliver Upton <oliver.upton@linux.dev>,
	James Morse <james.morse@arm.com>
Cc: Reiji Watanabe <reijiw@google.com>,
	kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org,
	Andrew Jones <andrew.jones@linux.dev>
Subject: Re: [PATCH v3 0/7] KVM: arm64: Use visibility hook to treat ID regs as RAZ
Date: Wed, 14 Sep 2022 11:41:50 +0100	[thread overview]
Message-ID: <166315210221.2105633.12201786772874832958.b4-ty@kernel.org> (raw)
In-Reply-To: <20220913094441.3957645-1-oliver.upton@linux.dev>

On Tue, 13 Sep 2022 09:44:33 +0000, Oliver Upton wrote:
> 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.
> 
> [...]

Applied to kvm-arm64/next, thanks!

[1/7] KVM: arm64: Use visibility hook to treat ID regs as RAZ
      commit: 34b4d20399e6fad2e3379b11e68dff1d1549274e
[2/7] KVM: arm64: Remove internal accessor helpers for id regs
      commit: 4782ccc8ef50fabb70bab9fa73186285dba6d91d
[3/7] KVM: arm64: Drop raz parameter from read_id_reg()
      commit: cdd5036d048ca96ef5212fb37f4f56db40cb1bc2
[4/7] KVM: arm64: Spin off helper for calling visibility hook
      commit: 5d9a718b64e428a40939806873ecf16f072008b3
[5/7] KVM: arm64: Add a visibility bit to ignore user writes
      commit: 4de06e4c1dc949c35c16e4423b4ccd735264b0a9
[6/7] KVM: arm64: Treat 32bit ID registers as RAZ/WI on 64bit-only system
      commit: d5efec7ed826b3b29c6847bf59383d8d07347a4e
[7/7] KVM: selftests: Add test for AArch32 ID registers
      commit: 797b84517c190053597e3f7e03ead15da872e04d

Cheers,

	M.
-- 
Marc Zyngier <maz@kernel.org>


      parent reply	other threads:[~2022-09-14 10:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13  9:44 [PATCH v3 0/7] KVM: arm64: Use visibility hook to treat ID regs as RAZ Oliver Upton
2022-09-13  9:44 ` [PATCH v3 1/7] " 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 ` Marc Zyngier [this message]

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=166315210221.2105633.12201786772874832958.b4-ty@kernel.org \
    --to=maz@kernel.org \
    --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=oliver.upton@linux.dev \
    --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