If your “FPState VSO” means something else (e.g., a specific library, a kernel feature, or a different product), please clarify and I will adapt the feature spec accordingly.
There is no universal "right" answer, but there is a strategic rule of thumb: fpstate vso
The bottom line: A VSO is your friend in the trenches. An FPSTATE attorney is your sniper for difficult targets. Do not let ego stop you from hiring an attorney if your claim is worth more than $50,000 in back pay. Most attorneys only get paid if you win, so they will only take your case if they believe in it. If your “FPState VSO” means something else (e
Traditionally, operating systems handled floating-point state with a static approach. When a task (process or thread) is context-switched out, the kernel needs to save the FPU/SIMD state to memory so the next task can use the registers. The bottom line: A VSO is your friend in the trenches
For decades, the size of this state was relatively small. However, modern CPUs have introduced massive register expansions:
Under the old model, the kernel often had to allocate memory based on the maximum possible size the CPU supported. If your CPU supported AMX but your application was a simple text editor using only legacy SSE instructions, the kernel was still allocating (and zeroing) space for the massive AMX registers. This led to memory bloat and wasted CPU cycles during context switches.