From: Christoph Hellwig <hch@infradead.org>
To: Will Deacon <will@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Ard Biesheuvel <ardb@google.com>,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
kernel-team@android.com, Mark Rutland <mark.rutland@arm.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Eric Biggers <ebiggers@google.com>,
Kees Cook <keescook@chromium.org>, Marc Zyngier <maz@kernel.org>,
Mark Brown <broonie@kernel.org>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v4 0/4] arm64: Run kernel mode NEON with preemption enabled
Date: Tue, 12 Dec 2023 08:35:36 -0800 [thread overview]
Message-ID: <ZXiL2FhAWozC4HVu@infradead.org> (raw)
In-Reply-To: <20231212105513.GA28416@willie-the-truck>
On Tue, Dec 12, 2023 at 10:55:13AM +0000, Will Deacon wrote:
> As discussed off-list, the vague concern was if kernel_neon_begin() is
> nested off the back of a user fault. The BUG_ON() should fire in that case,
> so we're all good.
I think we should really document all these rules, and Samuel's series
to add the portable FPU API would be the right place for it. I'd also
really love to see objtool support for enforcing the various rules
where possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-12-12 16:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 11:32 [PATCH v4 0/4] arm64: Run kernel mode NEON with preemption enabled Ard Biesheuvel
2023-12-08 11:32 ` [PATCH v4 1/4] arm64: fpsimd: Drop unneeded 'busy' flag Ard Biesheuvel
2023-12-12 11:27 ` Geert Uytterhoeven
2023-12-12 12:29 ` Will Deacon
2023-12-12 12:34 ` Geert Uytterhoeven
2023-12-12 12:59 ` Ard Biesheuvel
2023-12-12 13:54 ` Geert Uytterhoeven
2023-12-08 11:32 ` [PATCH v4 2/4] arm64: fpsimd: Preserve/restore kernel mode NEON at context switch Ard Biesheuvel
2023-12-08 11:32 ` [PATCH v4 3/4] arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD Ard Biesheuvel
2023-12-08 11:32 ` [PATCH v4 4/4] arm64: crypto: Disable yielding logic unless CONFIG_PREEMPT_VOLUNTARY=y Ard Biesheuvel
2023-12-11 20:27 ` [PATCH v4 0/4] arm64: Run kernel mode NEON with preemption enabled Will Deacon
2023-12-12 8:16 ` Ard Biesheuvel
2023-12-12 10:55 ` Will Deacon
2023-12-12 16:35 ` Christoph Hellwig [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=ZXiL2FhAWozC4HVu@infradead.org \
--to=hch@infradead.org \
--cc=ardb@google.com \
--cc=ardb@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=ebiggers@google.com \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).