From: Vincent Donnefort <vdonnefort@google.com>
To: Fuad Tabba <fuad.tabba@linux.dev>
Cc: Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Fuad Tabba <tabba@google.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] KVM: arm64: Support SVE in protected VMs
Date: Fri, 6 Nov 2026 17:58:03 +0000 [thread overview]
Message-ID: <au4VKxSnkJgDtcpG@google.com> (raw)
In-Reply-To: <20261105130456.1617185-1-fuad.tabba@linux.dev>
On Thu, Nov 05, 2026 at 01:04:52PM +0000, Fuad Tabba wrote:
> Hi folks,
>
> This series adds SVE support for protected VMs. EL2 allocates a
> protected vCPU's SVE state from its own heap rather than pinning the
> host's buffer, so the host never sees the guest's vector registers. It
> then advertises ID_AA64ZFR0_EL1 to protected VMs, and routes the SVE
> trap to the lazy FP switch. The first patch is a small tidy-up of the
> pKVM FP sync code that saves a guest's SVE state.
>
> v2 of the pKVM selftests series [1] will add a selftest for this.
>
> Based on Linux 7.4-rc1 (6628e7d4c6b25).
>
> Cheers,
> /fuad
>
> [1] https://lore.kernel.org/all/20261104084842.132944-1-fuad.tabba@linux.dev/
>
> Fuad Tabba (4):
> KVM: arm64: Remove redundant kern_hyp_va() calls from the pKVM FP sync
> KVM: arm64: Allocate a protected vCPU's SVE state at EL2
> KVM: arm64: Advertise ID_AA64ZFR0_EL1 to protected VMs
> KVM: arm64: Allow protected VMs to use SVE
>
> Documentation/virt/kvm/arm/pkvm.rst | 6 ++---
> arch/arm64/include/asm/kvm_hyp.h | 2 ++
> arch/arm64/include/asm/kvm_pkvm.h | 1 +
> arch/arm64/kvm/arm.c | 1 +
> arch/arm64/kvm/hyp/nvhe/hyp-main.c | 4 +--
> arch/arm64/kvm/hyp/nvhe/pkvm.c | 41 +++++++++++++++++++----------
> arch/arm64/kvm/hyp/nvhe/switch.c | 1 +
> arch/arm64/kvm/hyp/nvhe/sys_regs.c | 22 ++++++++++++++--
> arch/arm64/kvm/reset.c | 2 ++
> 9 files changed, 59 insertions(+), 21 deletions(-)
>
>
> base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
> --
> 2.47.3
>
For the whole series
Reviewed-by: Vincent Donnefort <vdonnefort@google.com>
Tested-by: Vincent Donnefort <vdonnefort@google.com>
--
Vincent
prev parent reply other threads:[~2026-11-06 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 13:04 Fuad Tabba
2026-11-05 13:04 ` [PATCH 1/4] KVM: arm64: Remove redundant kern_hyp_va() calls from the pKVM FP sync Fuad Tabba
2026-11-05 13:04 ` [PATCH 2/4] KVM: arm64: Allocate a protected vCPU's SVE state at EL2 Fuad Tabba
2026-11-06 17:51 ` Vincent Donnefort
2026-11-06 18:59 ` Oliver Upton
2026-11-05 13:04 ` [PATCH 3/4] KVM: arm64: Advertise ID_AA64ZFR0_EL1 to protected VMs Fuad Tabba
2026-11-05 13:04 ` [PATCH 4/4] KVM: arm64: Allow protected VMs to use SVE Fuad Tabba
2026-11-06 17:58 ` Vincent Donnefort [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=au4VKxSnkJgDtcpG@google.com \
--to=vdonnefort@google.com \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.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
all inboxes | Powered by JetHome®