From: "Bae, Chang Seok" <chang.seok.bae@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Borislav Petkov <bp@suse.de>, "luto@kernel.org" <luto@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@kernel.org" <mingo@kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"Brown, Len" <len.brown@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Liu, Jing2" <jing2.liu@intel.com>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v4 22/22] x86/fpu/xstate: Introduce boot-parameters to control state component support
Date: Sun, 21 Feb 2021 20:10:42 +0000 [thread overview]
Message-ID: <4862AEE9-1819-43A7-BF95-C02DB6E2D06D@intel.com> (raw)
In-Reply-To: <cb6151cf-8f71-2275-c757-098d163f87ff@infradead.org>
On Feb 21, 2021, at 11:30, Randy Dunlap <rdunlap@infradead.org> wrote:
> Can we tell people (in this Doc file) where to look up the values that can be
> used in xstate.enable and xstate.disable?
Perhaps add something like this with the change below:
“See comment before function fpu__init_parse_early_param() in
arch/x86/kernel/fpu/init.c."
/*
* The kernel parameter "xstate.enable='mask'" and "xstate.disable='mask'" have a
* mask value in a subset of XFEATURE_MASK_CONFIGURABLE.
*
* The longest parameter is 22 octal number characters with '0' prefix and an extra
* '\0' for termination.
*/
#define MAX_XSTATE_MASK_CHARS 24
/**
* fpu__init_parse_early_param() - parse the xstate kernel parameters
*
* Parse them early because fpu__init_system() is executed before
* parse_early_param().
*/
static void __init fpu__init_parse_early_param(void)
Thanks,
Chang
next prev parent reply other threads:[~2021-02-21 20:12 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 18:56 [PATCH v4 00/22] x86: Support Intel Advanced Matrix Extensions Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 01/22] x86/fpu/xstate: Modify the initialization helper to handle both static and dynamic buffers Chang S. Bae
2021-03-10 13:40 ` Borislav Petkov
2021-02-21 18:56 ` [PATCH v4 02/22] x86/fpu/xstate: Modify state copy helpers " Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 03/22] x86/fpu/xstate: Modify address finders " Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 04/22] x86/fpu/xstate: Modify the context restore helper " Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 05/22] x86/fpu/xstate: Add a new variable to indicate dynamic user states Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 06/22] x86/fpu/xstate: Add new variables to indicate dynamic xstate buffer size Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 07/22] x86/fpu/xstate: Calculate and remember dynamic xstate buffer sizes Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 08/22] x86/fpu/xstate: Convert the struct fpu 'state' field to a pointer Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 09/22] x86/fpu/xstate: Introduce helpers to manage the xstate buffer dynamically Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 10/22] x86/fpu/xstate: Define the scope of the initial xstate data Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 11/22] x86/fpu/xstate: Update the xstate save function to support dynamic states Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 12/22] x86/fpu/xstate: Update the xstate buffer address finder " Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 13/22] x86/fpu/xstate: Update the xstate context copy function " Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 14/22] x86/fpu/xstate: Expand the xstate buffer on the first use of dynamic user state Chang S. Bae
2021-03-20 22:13 ` Thomas Gleixner
2021-03-20 22:21 ` Andy Lutomirski
2021-03-23 21:01 ` Len Brown
2021-03-24 3:14 ` Liu, Jing2
2021-03-24 21:09 ` Len Brown
2021-03-24 21:26 ` Andy Lutomirski
2021-03-24 21:30 ` Dave Hansen
2021-03-24 21:42 ` Andy Lutomirski
2021-03-24 21:58 ` Dave Hansen
2021-03-24 22:12 ` Andy Lutomirski
2021-03-25 5:12 ` Liu, Jing2
2021-03-25 6:59 ` Bae, Chang Seok
2021-03-25 7:26 ` Liu, Jing2
2021-03-23 21:52 ` Bae, Chang Seok
2021-03-24 14:24 ` Dave Hansen
2021-03-29 13:14 ` Len Brown
2021-03-29 13:33 ` Thomas Gleixner
2021-03-29 15:43 ` Len Brown
2021-03-29 16:06 ` Len Brown
2021-03-29 17:43 ` Andy Lutomirski
2021-03-29 18:57 ` Len Brown
2021-03-29 18:49 ` Thomas Gleixner
2021-03-29 22:16 ` Len Brown
2021-03-30 8:28 ` Thomas Gleixner
2021-03-30 16:38 ` Len Brown
2021-03-26 16:34 ` Jann Horn
2021-03-29 18:14 ` Bae, Chang Seok
2021-02-21 18:56 ` [PATCH v4 15/22] x86/fpu/xstate: Support ptracer-induced xstate buffer expansion Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 16/22] x86/fpu/xstate: Extend the table to map state components with features Chang S. Bae
2021-03-20 21:25 ` Thomas Gleixner
2021-03-23 21:52 ` Bae, Chang Seok
2021-02-21 18:56 ` [PATCH v4 17/22] x86/cpufeatures/amx: Enumerate Advanced Matrix Extension (AMX) feature bits Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 18/22] x86/fpu/amx: Define AMX state components and have it used for boot-time checks Chang S. Bae
2021-03-20 21:31 ` Thomas Gleixner
2021-03-23 21:52 ` Bae, Chang Seok
2021-02-21 18:56 ` [PATCH v4 19/22] x86/fpu/amx: Enable the AMX feature in 64-bit mode Chang S. Bae
2021-03-20 21:26 ` Thomas Gleixner
2021-03-23 21:51 ` Bae, Chang Seok
2021-02-21 18:56 ` [PATCH v4 20/22] selftest/x86/amx: Include test cases for the AMX state management Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 21/22] x86/fpu/xstate: Support dynamic user state in the signal handling path Chang S. Bae
2021-02-21 18:56 ` [PATCH v4 22/22] x86/fpu/xstate: Introduce boot-parameters to control state component support Chang S. Bae
2021-02-21 19:30 ` Randy Dunlap
2021-02-21 20:10 ` Bae, Chang Seok [this message]
2021-02-21 20:37 ` Randy Dunlap
2021-03-20 20:56 ` Thomas Gleixner
2021-03-25 22:59 ` Len Brown
2021-03-25 23:10 ` Dave Hansen
2021-03-26 15:27 ` Len Brown
2021-03-26 19:22 ` Thomas Gleixner
2021-03-26 1:41 ` Andy Lutomirski
2021-03-26 15:33 ` Len Brown
2021-03-26 15:48 ` Andy Lutomirski
2021-03-26 17:53 ` Len Brown
2021-03-26 18:12 ` Andy Lutomirski
2021-03-27 4:53 ` Len Brown
2021-03-27 22:20 ` Thomas Gleixner
2021-03-29 13:31 ` Len Brown
2021-03-29 14:10 ` Thomas Gleixner
2021-03-26 18:17 ` Borislav Petkov
2021-03-27 4:41 ` Len Brown
2021-03-26 1:50 ` Thomas Gleixner
2021-03-26 15:36 ` Len Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4862AEE9-1819-43A7-BF95-C02DB6E2D06D@intel.com \
--to=chang.seok.bae@intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=jing2.liu@intel.com \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=ravi.v.shankar@intel.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®