Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Fuad Tabba <tabba@google.com>, James Morse <james.morse@arm.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mostafa Saleh <smostafa@google.com>,
	Oliver Upton <oupton@kernel.org>,
	Sebastian Ott <sebott@redhat.com>,
	Steffen Eiden <seiden@linux.ibm.com>,
	Sudeep Holla <sudeep.holla@kernel.org>,
	Vincent Donnefort <vdonnefort@google.com>,
	Wei-Lin Chang <weilin.chang@arm.com>,
	Will Deacon <will@kernel.org>,
	Yuan Yao <yaoyuan@linux.alibaba.com>,
	Joey Gouly <joey.gouly@arm.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 7.1, take #2
Date: Thu,  7 May 2026 16:42:21 +0100	[thread overview]
Message-ID: <20260507154221.2905554-1-maz@kernel.org> (raw)

Paolo,

Here's the second set of KVM/arm64 fixes for 7.1. Nothing too horrible
this time, aside from an ARM erratum workaround that has little impact
on KVM, but relies on some firmware dealing with the problem. Bleh.

The rest is a small collection of bug fixes, mostly affecting the MMU
(permission fault handling with guest_memfd, 52bit VA with NV), and a
small set of AI-enhanced fixes from Fuad. I guess I'll have to get
used to that.

And last but not least, Steffen joins the merry band of KVM/arm64
reviewers in preparation of s390 and arm64 being joined at the hip...

Please pull,

	M.

The following changes since commit 7fd2df204f342fc17d1a0bfcd474b24232fb0f32:

  Linux 7.1-rc2 (2026-05-03 14:21:25 -0700)

are available in the Git repository at:

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

for you to fetch changes up to effc0a39b8e0f30670fe24f51e44329d4324e566:

  KVM: arm64: Pre-check vcpu memcache for host->guest donate (2026-05-07 14:12:42 +0100)

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

- Add the pKVM side of the workaround for ARM's erratum 4193714, provided
  that the EL3 firmware does its part of the job. KVM will refuse to
  initialise otherwise.

- Correctly handle 52bit VAs for guest EL2 stage-1 translations when
  running under NV with E2H==0.

- Correctly deal with permission faults in guest_memfd memslots.

- Fix the steal-time selftest after the infrastructure was reworked.

- Make sure the host cannot pass a non-sensical clock update to the
  EL2 tracing infrastructure.

- Appoint Steffen Eiden as a reviewer in anticipation of the KVM/s390
  ability to run arm64 guests, which will inevitably lead to arm64
  code being directly used on s390.

- Make sure that EL2 is configured with both exception entry and exit
  being Context Synchronization Events.

- Handle the current vcpu being NULL on EL2 panic.

- Fix the selftest_vcpu memcache being empty at the point of donation or
  sharing.

- Check that the memcache has enough capacity before engaging on the
  share/donate path.

- Fix __deactivate_fgt() to use its parameter rather than a variable
  in the macro context.

----------------------------------------------------------------
Alexandru Elisei (1):
      KVM: arm64: Handle permission faults with guest_memfd

Fuad Tabba (6):
      KVM: arm64: Make EL2 exception entry and exit context-synchronization events
      KVM: arm64: Guard against NULL vcpu on VHE hyp panic path
      KVM: arm64: Fix __deactivate_fgt macro parameter typo
      KVM: arm64: Seed pkvm_ownership_selftest vcpu memcache
      KVM: arm64: Pre-check vcpu memcache for host->guest share
      KVM: arm64: Pre-check vcpu memcache for host->guest donate

James Morse (1):
      KVM: arm64: Work around C1-Pro erratum 4193714 for protected guests

Mostafa Saleh (1):
      KVM: arm64: Remove potential UB on nvhe tracing clock update

Sebastian Ott (1):
      KVM: selftests: arm64: Fix steal_time test after UAPI refactoring

Steffen Eiden (1):
      MAINTAINERS: Add Steffen as reviewer for KVM/arm64

Wei-Lin Chang (1):
      KVM: arm64: nv: Consider the DS bit when translating TCR_EL2

 MAINTAINERS                              |  1 +
 arch/arm64/include/asm/kvm_nested.h      |  1 +
 arch/arm64/include/asm/sysreg.h          |  2 +-
 arch/arm64/kvm/arm.c                     | 21 ++++++++++++++
 arch/arm64/kvm/hyp/include/hyp/switch.h  |  2 +-
 arch/arm64/kvm/hyp/nvhe/clock.c          |  3 ++
 arch/arm64/kvm/hyp/nvhe/mem_protect.c    | 47 +++++++++++++++++++++++++++++++-
 arch/arm64/kvm/hyp/nvhe/pkvm.c           | 16 ++++++++++-
 arch/arm64/kvm/hyp/vhe/switch.c          |  3 +-
 arch/arm64/kvm/mmu.c                     | 29 ++++++++++++++------
 include/linux/arm-smccc.h                |  6 ++++
 tools/testing/selftests/kvm/steal_time.c |  2 ++
 12 files changed, 120 insertions(+), 13 deletions(-)


                 reply	other threads:[~2026-05-07 15:42 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=20260507154221.2905554-1-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=alexandru.elisei@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=oupton@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sebott@redhat.com \
    --cc=seiden@linux.ibm.com \
    --cc=smostafa@google.com \
    --cc=sudeep.holla@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.com \
    --cc=vdonnefort@google.com \
    --cc=weilin.chang@arm.com \
    --cc=will@kernel.org \
    --cc=yaoyuan@linux.alibaba.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