From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] arm64: fpsimd: improve stacking logic in non-interruptible context
Date: Fri, 9 Dec 2016 18:07:56 +0000 [thread overview]
Message-ID: <20161209180756.GA21051@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <20161209172407.GC1574@e103592.cambridge.arm.com>
On Fri, Dec 09, 2016 at 05:24:08PM +0000, Dave P Martin wrote:
> On Fri, Dec 09, 2016 at 04:46:32PM +0000, Ard Biesheuvel wrote:
> > Currently, we allow kernel mode NEON in softirq or hardirq context by
> > stacking and unstacking a slice of the NEON register file for each call
> > to kernel_neon_begin() and kernel_neon_end(), respectively.
> >
> > Given that
> > a) a CPU typically spends most of its time in userland, during which time
> > no kernel mode NEON in process context is in progress,
> > b) a CPU spends most of its time in the kernel doing other things than
> > kernel mode NEON when it gets interrupted to perform kernel mode NEON
> > in softirq context
> >
> > the stacking and subsequent unstacking is only necessary if we are
> > interrupting a thread while it is performing kernel mode NEON in process
> > context, which means that in all other cases, we can simply preserve the
> > userland FPSIMD state once, and only restore it upon return to userland,
> > even if we are being invoked from softirq or hardirq context.
> >
> > So instead of checking whether we are running in interrupt context, keep
> > track of the level of nested kernel mode NEON calls in progress, and only
> > perform the eager stack/unstack if the level exceeds 1.
> >
> > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> This looks good to me.
>
> This should also make the SVE case trivial now: there can only be live
> SVE state when in process context with !TIF_FOREIGN_FPSTATE, and the
> SVE save/restore is then handled by fpsimd_{save,load}_state()
> directly. For deeper nesting levels, there is already no live SVE
> state, so kernel_neon_{save,load}_partial_state() are enough in that
> case.
That's still tricky for SVE. If you get an interrupt in
kernel_neon_begin_partial() after the level has been incremented to 1
but before fpsimd_save_state() has been called, SVE-unaware
kernel_neon_{save,load}_partial_state() would corrupt the SVE state.
--
Catalin
next prev parent reply other threads:[~2016-12-09 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 16:46 [PATCH v4] arm64: fpsimd: improve stacking logic in non-interruptible context Ard Biesheuvel
2016-12-09 17:24 ` Dave Martin
2016-12-09 18:07 ` Catalin Marinas [this message]
2016-12-09 18:21 ` Catalin Marinas
2016-12-09 19:29 ` Dave Martin
2016-12-09 20:57 ` Ard Biesheuvel
2016-12-12 10:35 ` Dave Martin
2016-12-12 17:55 ` Ard Biesheuvel
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=20161209180756.GA21051@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).