Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752760AbcD2Tnq (ORCPT ); Fri, 29 Apr 2016 15:43:46 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:35869 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752439AbcD2Tnn (ORCPT ); Fri, 29 Apr 2016 15:43:43 -0400 Date: Fri, 29 Apr 2016 21:43:38 +0200 From: Ingo Molnar To: Dave Hansen Cc: Yu-cheng Yu , x86@kernel.org, "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, Andy Lutomirski , Borislav Petkov , Sai Praneeth Prakhya , "Ravi V. Shankar" , Fenghua Yu Subject: Re: [PATCH v4 0/10] x86/xsaves: Fix XSAVES known issues Message-ID: <20160429194338.GA22509@gmail.com> References: <5723A353.7060209@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5723A353.7060209@linux.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 Content-Length: 619 Lines: 19 * Dave Hansen wrote: > Hi Folks, > > I've heard through the grapevine that there's some concern that we > should not be bothering to enable XSAVES because there's not a > sufficient use case for it. [...] So I have no fundamental objections against this series - I didn't apply it back in March because not all patches had your Reviewed-by tag. Basically after you sorted out all the XSAVE dynamic feature detection/sizing issues I was a happy camper and have no objection against XSAVES. Could you please send a refreshed version against the latestest tip:master? Thanks, Ingo