Thread (71 messages) flat view 71 messages, 11 authors, 2018-10-16

Re: [RFC PATCH v4 02/27] x86/fpu/xstate: Change some names to separate XSAVES system and user states

From: Dave Hansen <dave.hansen@linux.intel.com>
Date: 2018-10-02 16:30:59
Also in: linux-arch, linux-doc, linux-mm, lkml

On 10/02/2018 09:21 AM, Yu-cheng Yu wrote:
On Tue, 2018-10-02 at 17:29 +0200, Borislav Petkov wrote:
quoted
On Fri, Sep 21, 2018 at 08:03:26AM -0700, Yu-cheng Yu wrote:
quoted
To support XSAVES system states, change some names to distinguish
user and system states.
I don't understand what the logic here is. SDM says:

XSAVES—Save Processor Extended States Supervisor

the stress being on "Supervisor" - why does it need to be renamed to
"system" now?
Good point.  However, "system" is more indicative; CET states are per-task and
not "Supervisor".  Do we want to go back to "Supervisor" or add comments?
This is one of those things where the SDM language does not match what
we use in the kernel.  I think it's fine to call them "system" or
"kernel" states to make it consistent with our existing in-kernel
nomenclature.

I say add comments to clarify what the SDM calls it vs. what we do.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help