From: John Haxby <john.haxby@oracle.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>, Andi Kleen <ak@linux.intel.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: x86@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, John Haxby <john.haxby@oracle.com>
Subject: [PATCH 0/1] x86/fpu: Allow clearcpuid= to clear several bits
Date: Wed, 22 Apr 2020 13:03:18 +0100 [thread overview]
Message-ID: <cover.1587555769.git.john.haxby@oracle.com> (raw)
Back in the mists of time, well, prior to 4.14.9, you could put clearcpuid=N
several times on the command line to clear several CPUID bits. Unfortunately,
there was a problem with the way that this was done which meant XSAVE, in
particular, wasn't cleared early enough. This was fixed in 0c2a3913d6f5
("x86/fpu: Parse clearcpuid= as early XSAVE argument"). Unfortunately that
also meant that only one bit could be cleared.
This patch mostly fixes that. Gone is the old, anachronistic, multiple
clearcpuid= arguments to be replaced by a single clearcpuid=BITNUM[,BITNUM,...]
argument. It's no longer possible to clear perhaps dozens of flags with a very
long kernel command line, but you can clear up to about eight bits now instead
of just one.
jch
John Haxby (1):
x86/fpu: Allow clearcpuid= to clear several bits
.../admin-guide/kernel-parameters.txt | 24 ++++++++++---------
arch/x86/kernel/fpu/init.c | 18 ++++++++------
2 files changed, 24 insertions(+), 18 deletions(-)
--
2.25.3
next reply other threads:[~2020-04-22 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 12:03 John Haxby [this message]
2020-04-22 12:03 ` [PATCH 1/1] x86/fpu: Allow clearcpuid= to clear several bits John Haxby
2020-04-22 14:35 ` Andi Kleen
2020-04-22 15:21 ` John Haxby
2020-04-23 1:41 ` Andi Kleen
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=cover.1587555769.git.john.haxby@oracle.com \
--to=john.haxby@oracle.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).