public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@linux.intel.com>
To: Yu-cheng Yu <yu-cheng.yu@intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Cc: Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@suse.de>,
	Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>,
	"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
	Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH v3 9/9] x86/xsaves: Re-enable XSAVES
Date: Tue, 1 Mar 2016 15:56:12 -0800	[thread overview]
Message-ID: <56D62C1C.3050806@linux.intel.com> (raw)
In-Reply-To: <787ba3e73f657b06c02464ae522a47905ed503b8.1456524359.git.yu-cheng.yu@intel.com>

On 02/29/2016 09:42 AM, Yu-cheng Yu wrote:
>  	/*
> -	 * Quirk: we don't yet handle the XSAVES* instructions
> -	 * correctly, as we don't correctly convert between
> -	 * standard and compacted format when interfacing
> -	 * with user-space - so disable it for now.
> -	 *
> -	 * The difference is small: with recent CPUs the
> -	 * compacted format is only marginally smaller than
> -	 * the standard FPU state format.
> -	 *
> -	 * ( This is easy to backport while we are fixing
> -	 *   XSAVES* support. )
> +	 * Most recent CPUs supporting XSAVES can run 64-bit mode.
> +	 * Enable XSAVES for 64-bit.
>  	 */
> -	setup_clear_cpu_cap(X86_FEATURE_XSAVES);
> +	if (!config_enabled(CONFIG_X86_64))
> +		setup_clear_cpu_cap(X86_FEATURE_XSAVES);
>  }

I think we need a much better explanation of this for posterity.  Why
are we not supporting this now, and what would someone have to do in the
future in order to enable it?

>  /*
> diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/xstate.c
> index 2e80d6f..cb2a484 100644
> --- a/arch/x86/kernel/fpu/xstate.c
> +++ b/arch/x86/kernel/fpu/xstate.c
> @@ -204,6 +204,14 @@ void fpu__init_cpu_xstate(void)
>  	if (!cpu_has_xsave || !xfeatures_mask)
>  		return;
>  
> +	/*
> +	 * Make it clear that XSAVES supervisor states are not yet
> +	 * implemented should anyone expect it to work by changing
> +	 * bits in XFEATURE_MASK_* macros and XCR0.
> +	 */
> +	WARN_ONCE((xfeatures_mask & XFEATURE_MASK_SUPERVISOR),
> +		"x86/fpu: XSAVES supervisor states are not yet implemented.\n");
> +
>  	cr4_set_bits(X86_CR4_OSXSAVE);
>  	xsetbv(XCR_XFEATURE_ENABLED_MASK, xfeatures_mask);
>  }

Let's also do a:

	xfeatures_mask &= ~XFEATURE_MASK_SUPERVISOR;

Otherwise, we have a broken system at the moment.

  reply	other threads:[~2016-03-02  0:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 17:41 [PATCH v3 0/9] x86/xsaves: Fix XSAVES known issues Yu-cheng Yu
2016-02-29 17:41 ` [PATCH v3 1/9] x86/xsaves: Define and use user_xstate_size for xstate size in signal context Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 2/9] x86/xsaves: Rename xstate_size to kernel_xstate_size to explicitly distinguish xstate size in kernel from user space Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 3/9] x86/xsaves: Keep init_fpstate.xsave.header.xfeatures as zero for init optimization Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 4/9] x86/xsaves: Introduce a new check that allows correct xstates copy from kernel to user directly Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 5/9] x86/xsaves: Align xstate components according to CPUID Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 6/9] x86/xsaves: Supervisor state component offset Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 7/9] x86/xsaves: Fix PTRACE frames for XSAVES Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 8/9] x86/xsaves: Fix XSTATE component offset print out Yu-cheng Yu
2016-02-29 17:42 ` [PATCH v3 9/9] x86/xsaves: Re-enable XSAVES Yu-cheng Yu
2016-03-01 23:56   ` Dave Hansen [this message]
2016-03-02  0:34     ` Yu-cheng Yu
2016-03-02  0:45       ` Dave Hansen
2016-03-02  0:48         ` Yu-cheng Yu
2016-03-02  0:53         ` H. Peter Anvin
2016-03-02  0:58           ` Yu-cheng Yu

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=56D62C1C.3050806@linux.intel.com \
    --to=dave.hansen@linux.intel.com \
    --cc=bp@suse.de \
    --cc=fenghua.yu@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=ravi.v.shankar@intel.com \
    --cc=sai.praneeth.prakhya@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yu-cheng.yu@intel.com \
    /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