Just nitpicks:
On Sun, Jan 17, 2021 at 10:20:38PM -0800, Andy Lutomirski wrote:
> Currently, requesting kernel FPU access doesn't distinguish which parts of
> the extended ("FPU") state are needed. This is nice for simplicity, but
> there are a few cases in which it's suboptimal:
>
> - The
From: Andy Lutomirski
> Sent: 18 January 2021 06:21
>
> Currently, requesting kernel FPU access doesn't distinguish which parts of
> the extended ("FPU") state are needed. This is nice for simplicity, but
> there are a few cases in which it's suboptimal:
>
> - The vast majority of in-kernel
On Sun, Jan 17, 2021 at 10:20:38PM -0800, Andy Lutomirski wrote:
> - Code that wants MMX doesn't want need MXCSR or FCW initialized.
>_mmx_memcpy(), for example, can run before CR4.OSFXSR gets set, and
>initializing MXCSR will fail.
> +#define KFPU_MMX 0 /* nothing
Currently, requesting kernel FPU access doesn't distinguish which parts of
the extended ("FPU") state are needed. This is nice for simplicity, but
there are a few cases in which it's suboptimal:
- The vast majority of in-kernel FPU users want XMM/YMM/ZMM state but do
not use legacy 387
4 matches
Mail list logo