From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752552AbdAXIIX (ORCPT ); Tue, 24 Jan 2017 03:08:23 -0500 Received: from mail-wm0-f68.google.com ([74.125.82.68]:33119 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752443AbdAXIIU (ORCPT ); Tue, 24 Jan 2017 03:08:20 -0500 Date: Tue, 24 Jan 2017 09:08:10 +0100 From: Ingo Molnar To: Kevin Hao Cc: Dave Hansen , Yu-cheng Yu , fenghua.yu@intel.com, dvlasenk@redhat.com, peterz@infradead.org, oleg@redhat.com, linux-kernel@vger.kernel.org, brgerst@gmail.com, luto@kernel.org, bp@alien8.de, jpoimboe@redhat.com, hpa@zytor.com, quentin.casasnovas@oracle.com, tglx@linutronix.de, torvalds@linux-foundation.org, riel@redhat.com, linux-tip-commits@vger.kernel.org Subject: Re: [tip:x86/urgent] x86/fpu: Set the xcomp_bv when we fake up a XSAVES area Message-ID: <20170124080810.GA11694@gmail.com> References: <20170123165529.GA4996@test-lenovo> <2be814b7-9fd6-7955-b4e3-6ecb4ef76052@linux.intel.com> <20170123205725.GA3920@test-lenovo> <90b0fbee-273b-31c2-6fe9-228f00c0a205@linux.intel.com> <20170123211640.GA3976@test-lenovo> <20170124001447.GD15017@pek-khao-d1> <0d717394-eaf0-4d29-1aae-218ffcc8f06b@linux.intel.com> <20170124015012.GA9969@pek-khao-d1> <1b4e8b6c-c143-1867-712c-8b2e336a6ce0@linux.intel.com> <20170124020921.GC9969@pek-khao-d1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170124020921.GC9969@pek-khao-d1> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Kevin Hao wrote: > > other than helping to hide bugs? > > Why do you think it hide the bug? In contrast, I think my patch fixes what the > bug really is. The memory area we fake up is bug, we should fix it there. The intention is to have a single FPU format set at bootup and xcomp_bv is essentially an invariant (constant) inherited by all tasks from early boot. In that sense setting xsave.header.xcomp_bv in copyin_to_xsaves() is misplaced. So I combined the two commits: I kept your original fix but applied Yu-cheng Yu's patch that moves the initialization from copyin_to_xsaves() to fpstate_init(). Thanks, Ingo