From: Andi Kleen <andi@firstfloor.org>
To: x86@kernel.org
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Support generic disabling of all XSAVE features
Date: Mon, 24 Jul 2017 17:43:48 -0700 [thread overview]
Message-ID: <20170725004353.5280-1-andi@firstfloor.org> (raw)
For performance testing and debugging it can be useful to disable XSAVE
features individually. This patchkit hooks up XSAVE with the
generic clearcpuid=... option, so that disabling a CPUID feature
automatically disables the respective XSAVE feature.
It also cleans up CPUID dependency management. Currently it's
possible to generate configurations with cleacpuid that crash.
It replaces an earlier patchkit that did this with special
case options.
v1:
Initial post
v2:
Work around broken lguest by exporting set_cpu_cap
Repost with cover letter
v3:
Repost. No changes to code.
v4:
Rebase to latest tree. Repost.
next reply other threads:[~2017-07-25 0:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 0:43 Andi Kleen [this message]
2017-07-25 0:43 ` [PATCH v4 1/5] x86/xsave: Move xsave initialization to after parsing early parameters Andi Kleen
2017-07-25 0:43 ` [PATCH v4 2/5] x86/cpuid: Add generic table for cpuid dependencies Andi Kleen
2017-07-25 0:43 ` [PATCH v4 3/5] x86/cpuid: Make clearcpuid an early param Andi Kleen
2017-07-25 0:43 ` [PATCH v4 4/5] x86/xsave: Make XSAVE check the base CPUID features before enabling Andi Kleen
2017-07-25 0:43 ` [PATCH v4 5/5] x86/xsave: Using generic CPUID clearing when disabling XSAVE Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2017-10-13 21:56 Support generic disabling of all XSAVE features Andi Kleen
2017-10-07 0:03 Andi Kleen
2017-10-05 21:52 Andi Kleen
2017-10-04 23:49 Andi Kleen
2017-09-19 22:26 Andi Kleen
2017-06-21 23:41 Andi Kleen
2017-06-07 23:29 Andi Kleen
2017-06-13 0:17 ` 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=20170725004353.5280-1-andi@firstfloor.org \
--to=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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).