From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Eric Biggers <ebiggers@kernel.org>,
x86@kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Ben Greear <greearb@candelatech.com>,
Xiao Liang <shaw.leon@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>
Subject: Re: [RFC PATCH v2] x86/fpu: make kernel-mode FPU reliably usable in softirqs
Date: Thu, 6 Mar 2025 13:09:47 +0100 [thread overview]
Message-ID: <20250306120947.GF16878@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <Z8gUYamgBr4M5ZaB@gmail.com>
On Wed, Mar 05, 2025 at 10:07:45AM +0100, Ingo Molnar wrote:
> > From: Eric Biggers <ebiggers@google.com>
> > Alternatives considered:
> >
> > - Make kernel-mode FPU sections fully preemptible. This would require
> > growing task_struct by another struct fpstate which is more than 2K.
>
> So that's something that will probably happen once the kernel is built
> using APX anyway?
ISTR looking into this at some point for RT. I also have vague memories
of other architectures doing something similar, but its all a long time
ago.
prev parent reply other threads:[~2025-03-06 12:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 20:49 [RFC PATCH v2] x86/fpu: make kernel-mode FPU reliably usable in softirqs Eric Biggers
2025-03-05 9:07 ` Ingo Molnar
2025-03-05 16:55 ` Dave Hansen
2025-03-05 17:37 ` Ingo Molnar
2025-03-05 18:04 ` Dave Hansen
2025-03-05 18:13 ` Ingo Molnar
2025-03-05 21:22 ` David Laight
2025-03-05 17:39 ` Eric Biggers
2025-03-05 18:09 ` Ingo Molnar
2025-03-05 20:30 ` Eric Biggers
2025-03-06 11:42 ` Ingo Molnar
2025-03-06 12:09 ` Peter Zijlstra [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=20250306120947.GF16878@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@kernel.org \
--cc=greearb@candelatech.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=shaw.leon@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@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