public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	dave.hansen@linux.intel.com
Subject: Re: [PATCH] x86, fpu: do not BUG_ON() in early FPU code
Date: Wed, 20 Jul 2016 20:02:56 +0200	[thread overview]
Message-ID: <20160720180256.GA14435@gmail.com> (raw)
In-Reply-To: <20160720162328.A07B4C4B@viggo.jf.intel.com>


* Dave Hansen <dave@sr71.net> wrote:

> 
> From: Dave Hansen <dave.hansen@linux.intel.com>
> 
> I don't think it is really possible to have a system where CPUID
> enumerates support for XSAVE but that it does not have FP/SSE
> (they are "legacy" features and always present).
> 
> But, I did manage to hit this case in qemu when I enabled its
> somewhat shaky XSAVE support.  The bummer is that the FPU is set
> up before we parse the command-line or have *any* console support
> including earlyprintk.
> 
> So a BUG() here is worthless.  All it does it guarantee that
> if/when we hit this case we have an empty console.  So, remove
> the BUG() and try to limp along by disabling XSAVE and trying to
> continue.
> 
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> ---
> 
>  b/arch/x86/kernel/fpu/xstate.c |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff -puN arch/x86/kernel/fpu/xstate.c~x86-fpu-do-not-BUG_ON-early arch/x86/kernel/fpu/xstate.c
> --- a/arch/x86/kernel/fpu/xstate.c~x86-fpu-do-not-BUG_ON-early	2016-07-20 09:03:07.347941392 -0700
> +++ b/arch/x86/kernel/fpu/xstate.c	2016-07-20 09:17:15.001309137 -0700
> @@ -715,7 +715,8 @@ void __init fpu__init_system_xstate(void
>  
>  	if ((xfeatures_mask & XFEATURE_MASK_FPSSE) != XFEATURE_MASK_FPSSE) {
>  		pr_err("x86/fpu: FP/SSE not present amongst the CPU's xstate features: 0x%llx.\n", xfeatures_mask);
> -		BUG();
> +		fpu__init_disable_system_xstate();
> +		return;

Ok, but please put a comment there explaining why we are not stopping the system.

Thanks,

	Ingo

      reply	other threads:[~2016-07-20 18:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 16:23 [PATCH] x86, fpu: do not BUG_ON() in early FPU code Dave Hansen
2016-07-20 18:02 ` Ingo Molnar [this message]

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=20160720180256.GA14435@gmail.com \
    --to=mingo@kernel.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave@sr71.net \
    --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