From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-f197.google.com (mail-pl1-f197.google.com [209.85.214.197]) by kanga.kvack.org (Postfix) with ESMTP id DE69D6B0006 for ; Tue, 2 Oct 2018 12:30:58 -0400 (EDT) Received: by mail-pl1-f197.google.com with SMTP id b95-v6so3288264plb.10 for ; Tue, 02 Oct 2018 09:30:58 -0700 (PDT) Received: from mga12.intel.com (mga12.intel.com. [192.55.52.136]) by mx.google.com with ESMTPS id h20-v6si15034820pgh.573.2018.10.02.09.30.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Oct 2018 09:30:57 -0700 (PDT) Subject: Re: [RFC PATCH v4 02/27] x86/fpu/xstate: Change some names to separate XSAVES system and user states References: <20180921150351.20898-1-yu-cheng.yu@intel.com> <20180921150351.20898-3-yu-cheng.yu@intel.com> <20181002152903.GB29601@zn.tnic> From: Dave Hansen Message-ID: <498c8824-9255-96be-71c2-3ebfa684a9d3@linux.intel.com> Date: Tue, 2 Oct 2018 09:30:52 -0700 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: owner-linux-mm@kvack.org List-ID: To: Yu-cheng Yu , Borislav Petkov Cc: x86@kernel.org, "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-api@vger.kernel.org, Arnd Bergmann , Andy Lutomirski , Balbir Singh , Cyrill Gorcunov , Florian Weimer , "H.J. Lu" , Jann Horn , Jonathan Corbet , Kees Cook , Mike Kravetz , Nadav Amit , Oleg Nesterov , Pavel Machek , Peter Zijlstra , Randy Dunlap , "Ravi V. Shankar" , Vedvyas Shanbhogue On 10/02/2018 09:21 AM, Yu-cheng Yu wrote: > On Tue, 2018-10-02 at 17:29 +0200, Borislav Petkov wrote: >> On Fri, Sep 21, 2018 at 08:03:26AM -0700, Yu-cheng Yu wrote: >>> 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: >> >> XSAVESa??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.