From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758249AbbA2V0Y (ORCPT ); Thu, 29 Jan 2015 16:26:24 -0500 Received: from mx1.redhat.com ([209.132.183.28]:44442 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758123AbbA2V0W (ORCPT ); Thu, 29 Jan 2015 16:26:22 -0500 Message-ID: <54CAA572.6060206@redhat.com> Date: Thu, 29 Jan 2015 16:26:10 -0500 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Oleg Nesterov , Dave Hansen CC: Suresh Siddha , Andy Lutomirski , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Fenghua Yu , the arch/x86 maintainers , linux-kernel Subject: Re: [PATCH 1/3] x86, fpu: unlazy_fpu: don't reset thread.fpu_counter References: <54C2A245.4010307@redhat.com> <20150129210723.GA31584@redhat.com> <20150129210752.GB31584@redhat.com> In-Reply-To: <20150129210752.GB31584@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/29/2015 04:07 PM, Oleg Nesterov wrote: > It is not clear why the "else" branch clears ->fpu_counter, this makes > no sense. > > If use_eager_fpu() then this has no effect. Otherwise, if we actually > wanted to prevent fpu preload after the context switch we would need to > reset it unconditionally, even if __thread_has_fpu(). > > Signed-off-by: Oleg Nesterov Reviewed-by: Rik van Riel