Re: [RFC] Design considerations for XSAVE Extended Area getters/setters

[Jason Thorpe <thorpej%me.com@localhost>]

> On May 28, 2019, at 10:37 AM, Martin Husemann <martin%duskware.de@localhost> wrote:
> 
> Stupid question: since this is all very rare and non-performance critical,
> why isn't it done as a single register per call? Adding more registers
> when thy arrive in newer cpu variants, and not worrying about how they
> are saved (XSAVE or similar) nor what format is used in the kernel?

It would make things a bit awkward for core files.

-- thorpej