public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Yu-cheng Yu <yu-cheng.yu@intel.com>
Cc: x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org,
	Dave Hansen <dave.hansen@linux.intel.com>,
	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 00/10] x86/xsaves: Fix XSAVES known issues
Date: Wed, 24 Feb 2016 09:43:36 +0100	[thread overview]
Message-ID: <20160224084336.GB22868@gmail.com> (raw)
In-Reply-To: <1456167336-3637-1-git-send-email-yu-cheng.yu@intel.com>


* Yu-cheng Yu <yu-cheng.yu@intel.com> wrote:

> XSAVES is a kernel-mode instruction. It offers a compacted format and
> memory-write optimization. These patches fix known issues in the first
> implementation. They are intended for discussion and getting feedback
> before actually getting applied.  
> 
> Patch 1, 2, and 4 are for converting between kernel-mode xstate area and
> signal frames.
> 
> Patch 8 is for converting between kernel-mode xstate area and ptrace
> frames.
> 
> Patch 3 and 7 fix optimization issues introduced by XSAVES to the buffer
> init_fpstate.
> 
> Patch 5 and 6 are related to xstate component offsets.
> 
> Patch 9 fixes xstate area print out.
> 
> Patch 10 re-enables XSAVES.
> 
> Yu-cheng Yu (10):
>   x86/xsaves: Define and use user_xstate_size for xstate size in signal
>     context
>   x86/xsaves: Rename xstate_size to kernel_xstate_size to explicitly
>     distinguish xstate size in kernel from user space
>   x86/xsaves: Keep init_fpstate.xsave.header.xfeatures as zero for init
>     optimization
>   x86/xsaves: Introduce a new check that allows correct xstates copy
>     from kernel to user directly
>   x86/xsaves: Align xstate components according to CPUID
>   x86/xsaves: Supervisor state component offset
>   x86/xsaves: Fix init_fpstate.header.xcomp_bv
>   x86/xsaves: Fix PTRACE frames for XSAVES
>   x86/xsaves: Fix XSTATE component offset print out
>   x86/xsaves: Re-enable XSAVES
> 
>  arch/x86/include/asm/fpu/types.h  |   2 +
>  arch/x86/include/asm/fpu/xstate.h |   8 +-
>  arch/x86/include/asm/processor.h  |   3 +-
>  arch/x86/kernel/fpu/core.c        |   6 +-
>  arch/x86/kernel/fpu/init.c        |  32 +---
>  arch/x86/kernel/fpu/regset.c      |  56 ++++--
>  arch/x86/kernel/fpu/signal.c      |  69 ++++++-
>  arch/x86/kernel/fpu/xstate.c      | 388 +++++++++++++++++++++++++++++---------
>  8 files changed, 425 insertions(+), 139 deletions(-)

Small housekeeping request: could you please make sure your series is properly 
threaded for email clients? This submission was sent as singular patches, without 
any References header.

I don't even know how you coaxed git-send-email into doing that - did you use 
--no-thread?

The recommended flags are --thread --no-chain-reply-to.

Thanks!

	Ingo

  reply	other threads:[~2016-02-24  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 18:55 [PATCH 00/10] x86/xsaves: Fix XSAVES known issues Yu-cheng Yu
2016-02-24  8:43 ` Ingo Molnar [this message]
2016-02-24 16:27   ` 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=20160224084336.GB22868@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@suse.de \
    --cc=dave.hansen@linux.intel.com \
    --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