From: Breno Leitao <leitao@debian.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH] arm64/sve: Don't zero the SVE state buffer when the SVE state is live
Date: Tue, 15 Sep 2026 03:27:10 -0700 [thread overview]
Message-ID: <aqkdWl7NemLu_iim@gmail.com> (raw)
In-Reply-To: <aqkapYE-xtS91laq@J2N7QTR9R3>
On Tue, Sep 15, 2026 at 11:15:01AM +0100, Mark Rutland wrote:
> On Tue, Sep 15, 2026 at 02:50:27AM -0700, Breno Leitao wrote:
> > On Tue, Sep 15, 2026 at 09:39:24AM +0100, Mark Rutland wrote:
> >
> > I've also dropped few other lines, but kept the benchmark values I've
> > collected. Does this look better now?
>
> Yep, that looks good to me, with one minor nit below.
>
> With that fixed up, this all looks good. I assume you'll send a v2.
>
> > Author: Breno Leitao <leitao@debian.org>
> > Date: Fri Sep 11 02:57:34 2026 -0700
> >
> > arm64/sve: Don't zero the SVE state buffer when the SVE state is live
> >
> > Currently do_sve_acc() always zeroes current->thread.sve_state. This is
> > not necessary in the common case, and avoiding the zeroing has a
> > measurable impact on some benchmarks.
> >
> > In the common case where the task is not preempted and its state is not
> > altered by a tracer, do_sve_acc() will observe that TIF_FOREIGN_FPSTATE
> > is clear. In such cases, only the live register values matter, and the
> > in-memory copy is stale regardless of whether it is saved in
> > FP_STATE_FPSIMD format or FP_STATE_SVE format.
> >
> > This is worth doing because the SVE state is discarded on syscall entry,
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> That should say something like "It is worth skipping the zeroing
> because". We deleted the line saying that skipping the zeroing was safe,
> and so it's not clear what "this" is referring to.
Ack, thanks for the feedback. I will send a v2 shortly.
--breno
prev parent reply other threads:[~2026-09-15 10:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 12:53 Breno Leitao
2026-09-15 8:39 ` Mark Rutland
2026-09-15 9:50 ` Breno Leitao
2026-09-15 10:15 ` Mark Rutland
2026-09-15 10:27 ` Breno Leitao [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=aqkdWl7NemLu_iim@gmail.com \
--to=leitao@debian.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@meta.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
/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®