Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev
Cc: Marc Zyngier <maz@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>, Jan Kotas <jank@cadence.com>,
	Oliver Upton <oliver.upton@linux.dev>
Subject: [PATCH 0/2] KVM: arm64: Fixes for NV+SVE
Date: Fri, 26 Sep 2025 12:41:06 -0700	[thread overview]
Message-ID: <20250926194108.84093-1-oliver.upton@linux.dev> (raw)

After staring at the ZCR_EL2 handling for the issue Jan reported I
also spotted an ugly preemption bug because ZCR_EL2 residence is *very*
different from the other sysregs.

We could definitely get away with loading ZCR_ELx on the CPU at
vcpu_load() but I'd rather not given the amount of special treatment
that we need to do for it already.

In addition to that, I've taken the liberty of forging Marc's authorship
and SOB on the SVE exception fix, figured he wont mind :-)

Applies to kvmarm-6.18, tested with QEMU-TCG (only implementation >128
bit) with L0: VL=512, L1: VL=256, and L2: VL=128.

Marc Zyngier (1):
  KVM: arm64: nv: Don't advance PC when pending an SVE exception

Oliver Upton (1):
  KVM: arm64: nv: Don't treat ZCR_EL2 as a 'mapped' register

 arch/arm64/kvm/sys_regs.c | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)


base-commit: 10fd0285305d0b48e8a3bf15d4f17fc4f3d68cb6
-- 
2.39.5


             reply	other threads:[~2025-09-26 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-26 19:41 Oliver Upton [this message]
2025-09-26 19:41 ` [PATCH 1/2] KVM: arm64: nv: Don't treat ZCR_EL2 as a 'mapped' register Oliver Upton
2025-09-26 19:41 ` [PATCH 2/2] KVM: arm64: nv: Don't advance PC when pending an SVE exception Oliver Upton
2025-09-27 11:29 ` [PATCH 0/2] KVM: arm64: Fixes for NV+SVE Marc Zyngier

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=20250926194108.84093-1-oliver.upton@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=jank@cadence.com \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=maz@kernel.org \
    --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