Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Alexander Potapenko <glider@google.com>,
	Joey Gouly <joey.gouly@arm.com>, Mark Brown <broonie@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
	Shaoqin Huang <shahuang@redhat.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>,
	kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	kvm@vger.kernel.org
Subject: [GIT PULL] KVM/arm64 fixes for 6.12, take #2
Date: Fri, 11 Oct 2024 14:27:56 +0100	[thread overview]
Message-ID: <20241011132756.3793137-1-maz@kernel.org> (raw)

Paolo,

Here's the second set of fixes for 6.12.

We have a handful of fixes for the ID register configuration (I had
originally queued them for -rc1, and somehow managed to accidentally
drop the branch on the floor), our NV shadow page tables, the vgic,
and a fix for a regression introduced in -rc1.

As usual, details in the tag.

Please pull,

	M.

The following changes since commit a1d402abf8e3ff1d821e88993fc5331784fac0da:

  KVM: arm64: Fix kvm_has_feat*() handling of negative features (2024-10-03 19:35:27 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-6.12-2

for you to fetch changes up to df5fd75ee305cb5927e0b1a0b46cc988ad8db2b1:

  KVM: arm64: Don't eagerly teardown the vgic on init error (2024-10-11 13:40:25 +0100)

----------------------------------------------------------------
KVM/arm64 fixes for 6.12, take #2

- Fix the guest view of the ID registers, making the relevant fields
  writable from userspace (affecting ID_AA64DFR0_EL1 and ID_AA64PFR1_EL1)

- Correcly expose S1PIE to guests, fixing a regression introduced
  in 6.12-rc1 with the S1POE support

- Fix the recycling of stage-2 shadow MMUs by tracking the context
  (are we allowed to block or not) as well as the recycling state

- Address a couple of issues with the vgic when userspace misconfigures
  the emulation, resulting in various splats. Headaches courtesy
  of our Syzkaller friends

----------------------------------------------------------------
Marc Zyngier (2):
      Merge branch kvm-arm64/idregs-6.12 into kvmarm/fixes
      KVM: arm64: Don't eagerly teardown the vgic on init error

Mark Brown (1):
      KVM: arm64: Expose S1PIE to guests

Oliver Upton (5):
      KVM: arm64: Unregister redistributor for failed vCPU creation
      KVM: arm64: nv: Keep reference on stage-2 MMU when scheduled out
      KVM: arm64: nv: Do not block when unmapping stage-2 if disallowed
      KVM: arm64: nv: Punt stage-2 recycling to a vCPU request
      KVM: arm64: nv: Clarify safety of allowing TLBI unmaps to reschedule

Shameer Kolothum (1):
      KVM: arm64: Make the exposed feature bits in AA64DFR0_EL1 writable from userspace

Shaoqin Huang (4):
      KVM: arm64: Disable fields that KVM doesn't know how to handle in ID_AA64PFR1_EL1
      KVM: arm64: Use kvm_has_feat() to check if FEAT_SSBS is advertised to the guest
      KVM: arm64: Allow userspace to change ID_AA64PFR1_EL1
      KVM: selftests: aarch64: Add writable test for ID_AA64PFR1_EL1

 arch/arm64/include/asm/kvm_host.h                 |  7 +++
 arch/arm64/include/asm/kvm_mmu.h                  |  3 +-
 arch/arm64/include/asm/kvm_nested.h               |  4 +-
 arch/arm64/kvm/arm.c                              |  5 ++
 arch/arm64/kvm/hypercalls.c                       | 12 ++--
 arch/arm64/kvm/mmu.c                              | 15 ++---
 arch/arm64/kvm/nested.c                           | 53 +++++++++++++---
 arch/arm64/kvm/sys_regs.c                         | 75 +++++++++++++++++++++--
 arch/arm64/kvm/vgic/vgic-init.c                   | 28 +++++++--
 tools/testing/selftests/kvm/aarch64/set_id_regs.c | 16 ++++-
 10 files changed, 183 insertions(+), 35 deletions(-)

                 reply	other threads:[~2024-10-11 13:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20241011132756.3793137-1-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=broonie@kernel.org \
    --cc=glider@google.com \
    --cc=joey.gouly@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=oliver.upton@linux.dev \
    --cc=pbonzini@redhat.com \
    --cc=shahuang@redhat.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --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