From: Marc Zyngier <maz@kernel•org>
To: kvmarm@lists•linux.dev, linux-arm-kernel@lists•infradead.org,
kvm@vger•kernel.org
Cc: Steffen Eiden <seiden@linux•ibm.com>,
Joey Gouly <joey.gouly@arm•com>,
Suzuki K Poulose <suzuki.poulose@arm•com>,
Oliver Upton <oupton@kernel•org>,
Zenghui Yu <yuzenghui@huawei•com>,
Mark Rutland <mark.rutland@arm•com>,
Will Deacon <will@kernel•org>, Fuad Tabba <tabba@google•com>
Subject: [PATCH v2 0/2] KVM: arm64: nv: Reduce FP/SVE overhead on exception/exception return
Date: Wed, 20 May 2026 09:50:34 +0100 [thread overview]
Message-ID: <20260520085036.541666-1-maz@kernel.org> (raw)
This is the second version of this short series optimising away a lot
of unnecessary FPSIMD/SVE context switch with NV.
* From v1 [1]:
- New commit message on patch #2 (Mark)
- Additional comments and WARN_ON_ONCE() (Mark)
If nobody screams, I'll stick that into -next.
Thanks,
M.
[1] https://lore.kernel.org/r/20260512140755.3676306-1-maz@kernel.org
Marc Zyngier (2):
KVM: arm64: nv: Track L2 to L1 exception emulation
KVM: arm64: nv: Don't save/restore FP register during a nested ERET or
exception
arch/arm64/include/asm/kvm_host.h | 3 ++-
arch/arm64/kvm/emulate-nested.c | 4 ++++
arch/arm64/kvm/fpsimd.c | 23 +++++++++++++++++++++++
3 files changed, 29 insertions(+), 1 deletion(-)
--
2.47.3
next reply other threads:[~2026-05-20 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 8:50 Marc Zyngier [this message]
2026-05-20 8:50 ` [PATCH v2 1/2] KVM: arm64: nv: Track L2 to L1 exception emulation Marc Zyngier
2026-05-20 8:50 ` [PATCH v2 2/2] KVM: arm64: nv: Don't save/restore FP register during a nested ERET or exception Marc Zyngier
2026-05-20 11:02 ` Joey Gouly
2026-05-21 6:21 ` Marc Zyngier
2026-05-20 13:02 ` Mark Rutland
2026-05-21 6:35 ` Marc Zyngier
2026-05-21 7:07 ` [PATCH v2 0/2] KVM: arm64: nv: Reduce FP/SVE overhead on exception/exception return 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=20260520085036.541666-1-maz@kernel.org \
--to=maz@kernel$(echo .)org \
--cc=joey.gouly@arm$(echo .)com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=kvmarm@lists$(echo .)linux.dev \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=oupton@kernel$(echo .)org \
--cc=seiden@linux$(echo .)ibm.com \
--cc=suzuki.poulose@arm$(echo .)com \
--cc=tabba@google$(echo .)com \
--cc=will@kernel$(echo .)org \
--cc=yuzenghui@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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