From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755745AbcBXInm (ORCPT ); Wed, 24 Feb 2016 03:43:42 -0500 Received: from mail-wm0-f66.google.com ([74.125.82.66]:34011 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755550AbcBXInk (ORCPT ); Wed, 24 Feb 2016 03:43:40 -0500 Date: Wed, 24 Feb 2016 09:43:36 +0100 From: Ingo Molnar To: Yu-cheng Yu Cc: x86@kernel.org, "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, Dave Hansen , Andy Lutomirski , Borislav Petkov , Sai Praneeth Prakhya , "Ravi V. Shankar" , Fenghua Yu Subject: Re: [PATCH 00/10] x86/xsaves: Fix XSAVES known issues Message-ID: <20160224084336.GB22868@gmail.com> References: <1456167336-3637-1-git-send-email-yu-cheng.yu@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1456167336-3637-1-git-send-email-yu-cheng.yu@intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Yu-cheng Yu 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