From: Marc Zyngier <maz@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Zhang Lei <zhang.lei@jp.fujitsu.com>,
James Morse <james.morse@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Andre Przywara <andre.przywara@arm.com>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 0/8] arm64/sve: Clean up KVM integration and optimise syscalls
Date: Mon, 28 Nov 2022 08:47:00 +0000 [thread overview]
Message-ID: <86mt8bmpob.wl-maz@kernel.org> (raw)
In-Reply-To: <20221115094640.112848-1-broonie@kernel.org>
On Tue, 15 Nov 2022 09:46:32 +0000,
Mark Brown <broonie@kernel.org> wrote:
>
> This patch series attempts to clarify the tracking of which set of
> floating point registers we save on systems supporting SVE, particularly
> with reference to KVM, and then uses the results of this clarification
> to improve the performance of simple syscalls where we return directly
> to userspace in cases where userspace is using SVE.
Reviewed-by: Marc Zyngier <maz@kernel.org>
I expect this to go via the arm64 tree, please shout if that's not the
case.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-11-28 8:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 9:46 [PATCH v5 0/8] arm64/sve: Clean up KVM integration and optimise syscalls Mark Brown
2022-11-15 9:46 ` [PATCH v5 1/8] KVM: arm64: Discard any SVE state when entering KVM guests Mark Brown
2022-11-15 9:46 ` [PATCH v5 2/8] arm64/fpsimd: Track the saved FPSIMD state type separately to TIF_SVE Mark Brown
2022-11-15 9:46 ` [PATCH v5 3/8] arm64/fpsimd: Have KVM explicitly say which FP registers to save Mark Brown
2022-11-15 9:46 ` [PATCH v5 4/8] arm64/fpsimd: Stop using TIF_SVE to manage register saving in KVM Mark Brown
2022-11-15 9:46 ` [PATCH v5 5/8] arm64/fpsimd: Load FP state based on recorded data type Mark Brown
2022-11-15 9:46 ` [PATCH v5 6/8] arm64/fpsimd: SME no longer requires SVE register state Mark Brown
2022-11-15 9:46 ` [PATCH v5 7/8] arm64/sve: Leave SVE enabled on syscall if we don't context switch Mark Brown
2022-11-15 9:46 ` [PATCH v5 8/8] arm64/fp: Use a struct to pass data to fpsimd_bind_state_to_cpu() Mark Brown
2022-11-28 8:47 ` Marc Zyngier [this message]
2022-11-29 19:52 ` [PATCH v5 0/8] arm64/sve: Clean up KVM integration and optimise syscalls Will Deacon
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=86mt8bmpob.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=andre.przywara@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@kernel.org \
--cc=zhang.lei@jp.fujitsu.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