From: Andi Kleen <andi@firstfloor.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Support generic disabling of all XSAVE features
Date: Mon, 12 Jun 2017 17:17:20 -0700 [thread overview]
Message-ID: <87vao07ncf.fsf@firstfloor.org> (raw)
In-Reply-To: <20170607232939.27441-1-andi@firstfloor.org> (Andi Kleen's message of "Wed, 7 Jun 2017 16:29:34 -0700")
Andi Kleen <andi@firstfloor.org> writes:
Any comments on this patchkit? If there are no objections please merge.
-Andi
> 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
next prev parent reply other threads:[~2017-06-13 0:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 23:29 Support generic disabling of all XSAVE features Andi Kleen
2017-06-07 23:29 ` [PATCH v2 1/5] x86/xsave: Move xsave initialization to after parsing early parameters Andi Kleen
2017-06-07 23:29 ` [PATCH v2 2/5] x86/cpuid: Add generic table for cpuid dependencies Andi Kleen
2017-06-07 23:29 ` [PATCH v2 3/5] x86/cpuid: Make clearcpuid an early param Andi Kleen
2017-06-07 23:29 ` [PATCH v2 4/5] x86/xsave: Make XSAVE check the base CPUID features before enabling Andi Kleen
2017-06-07 23:29 ` [PATCH v2 5/5] x86/xsave: Using generic CPUID clearing when disabling XSAVE Andi Kleen
2017-06-13 0:17 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-06-21 23:41 Support generic disabling of all XSAVE features Andi Kleen
2017-07-25 0:43 Andi Kleen
2017-09-19 22:26 Andi Kleen
2017-10-04 23:49 Andi Kleen
2017-10-05 21:52 Andi Kleen
2017-10-07 0:03 Andi Kleen
2017-10-13 21:56 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=87vao07ncf.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.