Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Fuad Tabba <tabba@google.com>
To: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Cc: maz@kernel.org, oliver.upton@linux.dev, will@kernel.org,
	 joey.gouly@arm.com, suzuki.poulose@arm.com,
	yuzenghui@huawei.com,  catalin.marinas@arm.com,
	vladimir.murzin@arm.com, tabba@google.com
Subject: [PATCH v5 0/9] KVM: arm64: Fixes for guest CPU feature trapping and enabling
Date: Tue, 18 Nov 2025 10:37:57 +0000	[thread overview]
Message-ID: <20251118103807.707500-1-tabba@google.com> (raw)

Hi,

This series contains several fixes for guest feature trapping and
enabling, as well as a bit of tidying up.

Changes from v3 [1]:
- Add a map of KVM capabilities to IOCTLs (Oliver)
- Based on Linux 6.18-rc6

Cheers,
/fuad

[1] https://lore.kernel.org/all/20251110134525.3768197-1-tabba@google.com/

Fuad Tabba (9):
  KVM: arm64: Fix Trace Buffer trapping for protected VMs
  KVM: arm64: Fix Trace Buffer trap polarity for protected VMs
  KVM: arm64: Fix MTE flag initialization for protected VMs
  KVM: arm64: Introduce helper to calculate fault IPA offset
  KVM: arm64: Include VM type when checking VM capabilities in pKVM
  KVM: arm64: Do not allow KVM_CAP_ARM_MTE for any guest in pKVM
  KVM: arm64: Track KVM IOCTLs and their associated KVM caps
  KVM: arm64: Check whether a VM IOCTL is allowed in pKVM
  KVM: arm64: Prevent host from managing timer offsets for protected VMs

 arch/arm64/include/asm/kvm_arm.h         |  2 ++
 arch/arm64/include/asm/kvm_host.h        | 42 ++++++++++++++++++++++++
 arch/arm64/include/asm/kvm_pkvm.h        | 33 ++++++++++++++++---
 arch/arm64/kvm/arch_timer.c              | 18 +++++++---
 arch/arm64/kvm/arm.c                     |  7 ++--
 arch/arm64/kvm/hyp/nvhe/pkvm.c           | 18 +++++-----
 arch/arm64/kvm/hyp/vgic-v2-cpuif-proxy.c |  2 +-
 arch/arm64/kvm/inject_fault.c            |  2 +-
 arch/arm64/kvm/mmu.c                     |  4 +--
 include/uapi/linux/kvm.h                 |  1 +
 10 files changed, 105 insertions(+), 24 deletions(-)


base-commit: 6a23ae0a96a600d1d12557add110e0bb6e32730c
-- 
2.52.0.rc1.455.g30608eb744-goog


             reply	other threads:[~2025-11-18 10:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18 10:37 Fuad Tabba [this message]
2025-11-18 10:37 ` [PATCH v5 1/9] KVM: arm64: Fix Trace Buffer trapping for protected VMs Fuad Tabba
2025-11-18 10:37 ` [PATCH v5 2/9] KVM: arm64: Fix Trace Buffer trap polarity " Fuad Tabba
2025-11-18 11:11   ` Suzuki K Poulose
2025-11-26 10:23   ` Marc Zyngier
2025-11-26 10:29     ` James Clark
2025-11-26 10:36       ` Fuad Tabba
2025-11-26 10:39         ` James Clark
2025-11-26 10:37     ` Fuad Tabba
2025-11-26 11:47       ` Marc Zyngier
2025-11-26 11:48         ` Fuad Tabba
2025-11-27 15:26           ` James Clark
2025-11-27 15:38             ` Fuad Tabba
2025-11-27 16:06               ` James Clark
2025-11-27 16:23                 ` Fuad Tabba
2025-11-18 10:38 ` [PATCH v5 3/9] KVM: arm64: Fix MTE flag initialization " Fuad Tabba
2025-11-18 10:38 ` [PATCH v5 4/9] KVM: arm64: Introduce helper to calculate fault IPA offset Fuad Tabba
2025-11-18 10:38 ` [PATCH v5 5/9] KVM: arm64: Include VM type when checking VM capabilities in pKVM Fuad Tabba
2025-11-26 10:52   ` Marc Zyngier
2025-11-26 11:00     ` Fuad Tabba
2025-11-26 15:36       ` Marc Zyngier
2025-11-26 17:05         ` Fuad Tabba
2025-11-18 10:38 ` [PATCH v5 6/9] KVM: arm64: Do not allow KVM_CAP_ARM_MTE for any guest " Fuad Tabba
2025-11-18 10:38 ` [PATCH v5 7/9] KVM: arm64: Track KVM IOCTLs and their associated KVM caps Fuad Tabba
2025-11-18 10:38 ` [PATCH v5 8/9] KVM: arm64: Check whether a VM IOCTL is allowed in pKVM Fuad Tabba
2025-11-18 10:38 ` [PATCH v5 9/9] KVM: arm64: Prevent host from managing timer offsets for protected VMs Fuad Tabba
2025-11-18 10:39 ` [PATCH v5 0/9] KVM: arm64: Fixes for guest CPU feature trapping and enabling Fuad Tabba

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=20251118103807.707500-1-tabba@google.com \
    --to=tabba@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=suzuki.poulose@arm.com \
    --cc=vladimir.murzin@arm.com \
    --cc=will@kernel.org \
    --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