public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: x86@kernel.org
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: [PATCH v4 3/5] x86/cpuid: Make clearcpuid an early param
Date: Mon, 24 Jul 2017 17:43:51 -0700	[thread overview]
Message-ID: <20170725004353.5280-4-andi@firstfloor.org> (raw)
In-Reply-To: <20170725004353.5280-1-andi@firstfloor.org>

From: Andi Kleen <ak@linux.intel.com>

Make clearcpuid= an early param, to make sure it is parsed
before the XSAVE initialization. This allows to modify
XSAVE state by clearing specific CPUID bits.

Signed-off-by: Andi Kleen <ak@linux.intel.com>
---
 arch/x86/kernel/cpu/common.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index 60b7aa6330ed..600e0cf714b9 100644
--- a/arch/x86/kernel/cpu/common.c
+++ b/arch/x86/kernel/cpu/common.c
@@ -1285,7 +1285,7 @@ static __init int setup_disablecpuid(char *arg)
 
 	return 1;
 }
-__setup("clearcpuid=", setup_disablecpuid);
+early_param("clearcpuid", setup_disablecpuid);
 
 #ifdef CONFIG_X86_64
 struct desc_ptr idt_descr __ro_after_init = {
-- 
2.9.4

  parent reply	other threads:[~2017-07-25  0:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25  0:43 Support generic disabling of all XSAVE features Andi Kleen
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 ` Andi Kleen [this message]
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

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-4-andi@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=ak@linux.intel.com \
    --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