public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: NeilBrown <neilb@suse.de>,
	james.t.kukunas@linux.intel.com,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch] x86, avx: don't use avx instructions with "noxsave" boot param
Date: Tue, 31 Jul 2012 10:29:14 -0700	[thread overview]
Message-ID: <1343755754.2041.2.camel@sbsiddha-desk.sc.intel.com> (raw)
In-Reply-To: <50180B2A.6070602@zytor.com>

On Tue, 2012-07-31 at 09:43 -0700, H. Peter Anvin wrote:
> My main reason for thinking that it would be good to clear the bits is 
> that it plays a lot nicer with alternatives and with static_cpu_has().

Fair enough. Neil, can you please drop the previous patch and Peter,
please queue this for v3.6. Thanks.

---
From: Suresh Siddha <suresh.b.siddha@intel.com>
Subject: x86, avx: don't use avx instructions with "noxsave" boot param

Clear AVX, AVX2 features along with clearing XSAVE feature bits,
as part of the parsing "noxsave" parameter.

Fixes the kernel boot panic with "noxsave" boot parameter.

We could have checked cpu_has_osxsave along with cpu_has_avx etc, but Peter
mentioned clearing the feature bits will be better for uses like
static_cpu_has() etc.

Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: stable@kernel.org	# v3.5
---
 arch/x86/kernel/cpu/common.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index 46d8786..a5fbc3c 100644
--- a/arch/x86/kernel/cpu/common.c
+++ b/arch/x86/kernel/cpu/common.c
@@ -144,6 +144,8 @@ static int __init x86_xsave_setup(char *s)
 {
 	setup_clear_cpu_cap(X86_FEATURE_XSAVE);
 	setup_clear_cpu_cap(X86_FEATURE_XSAVEOPT);
+	setup_clear_cpu_cap(X86_FEATURE_AVX);
+	setup_clear_cpu_cap(X86_FEATURE_AVX2);
 	return 1;
 }
 __setup("noxsave", x86_xsave_setup);



  reply	other threads:[~2012-07-31 17:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-30 22:46 [patch] x86, avx: don't use avx instructions with "noxsave" boot param Suresh Siddha
2012-07-31  4:20 ` NeilBrown
2012-07-31  4:33   ` H. Peter Anvin
2012-07-31 16:27     ` Suresh Siddha
2012-07-31 16:43       ` H. Peter Anvin
2012-07-31 17:29         ` Suresh Siddha [this message]
2012-08-01 10:42           ` NeilBrown
2012-08-08 22:25           ` [tip:x86/urgent] x86, avx: don't use avx instructions with " noxsave" " tip-bot for Suresh Siddha

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=1343755754.2041.2.camel@sbsiddha-desk.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=hpa@zytor.com \
    --cc=james.t.kukunas@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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