Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp597660rwb; Thu, 1 Dec 2022 06:13:32 -0800 (PST) X-Google-Smtp-Source: AA0mqf7ISTHPQXNqtyeBl/IT5jO8twJX0zJyKQehgHbPuysMZ29HU0S9CT8M3pA4B59TLXV3Lnqd X-Received: by 2002:a05:6a00:4c0b:b0:562:ebc8:6195 with SMTP id ea11-20020a056a004c0b00b00562ebc86195mr47313414pfb.38.1669904011913; Thu, 01 Dec 2022 06:13:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669904011; cv=none; d=google.com; s=arc-20160816; b=Q8ZiU09rsMDIcLAtZOhZezCMSRUG1TYSc6aGfpSBmDa7QgpIMdN0+tXVHhxiJeto2C ocb7Q/05fiM/AJ4LlLBW+y1n3CaaTepG2qrHjC1gA9M1PuNOrHCajevWYylNFc4pck1b /veefhFCMCMAhUo0N5W8SK/DOoEqtGUPL5F/3KfdkQxhrzarN86Z5vfA19W7TMoB213i 74WAnwZaqhOUqTbAeuOrREkrST7RrtcLSl9EBK0MLFcuGyCMwuCjCsemMKLB34pdG3IV 6D8zTFEVjcbG6ysS9It4Ciukr2XQKdlNsL6rkyxbI/SpU0qIYwRkgzRxOAS7/pcl49zG G1RQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=ApPANv2Va7braS7bXufocHkeJ+lZ2OL7Q3yyavNJ3kM=; b=YGdVSpn6UVQCuYTQ4ZRiGmsEHQPXakdTv0XvvTLJXqD8BhxkA+0zEAV0LMyLPtudCo rOCilRLO+SuZDI1rHV7Gi75LnI/yUD2lrSWKl87p9QrwaOWMHRHSBSMCAdic30OYNVIx ggvS+upUW1+lu3msC7h0Cq/lpChpfK4Njqrd1yirBJvMgztUUi0tc81oDhdLRUTlfhd+ 9r1QHAg2/tvXirBqhXEtqWHtRhkUkCwy0hg4XOlJz0uW+pE9zzupCiVbLi3E3/fQU4fy ER1QjU9xWNJwZWZ7c6AOzED5VBgRUigX0znKqSaWw295q+k72BQlrQnu1apElpcGFR9k 2mQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=bNDp34sZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x10-20020a170902ea8a00b00188fe19d3dbsi4335988plb.163.2022.12.01.06.13.19; Thu, 01 Dec 2022 06:13:31 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=bNDp34sZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231397AbiLAOGz (ORCPT + 83 others); Thu, 1 Dec 2022 09:06:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49318 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231792AbiLAOGf (ORCPT ); Thu, 1 Dec 2022 09:06:35 -0500 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0CECAA51A8; Thu, 1 Dec 2022 06:06:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1669903566; x=1701439566; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=WMGpqOgGqrVnBeh6UzML2xLvqnpofIMwJed+MAd9/yQ=; b=bNDp34sZzIgc7ao+P7B1kclcl4P4ETABkflFwmHOaAB8AcZlDGVFAy/L DPtKr49nm0101AFQJPHy1JOLJ125l8kyHH88e9d21Jij0ARcLxHrf4xiL QBoBxy3eBjBQ8PLKTVUyVbkyuGZ7QvyRZ3UObuT+LTJzdSHWrLIcPFRn6 qgBz86+lZOc4DeQcqHXBvUveHoEYkZEvWCm/cu3jwZFKOfasLZVuZKhIS i/Jf90ooHW8SNv7lR4fEdA1l5646l0E0EaQyFWd6SzPxswlOFng9LZAzA dBfTl9DgTu9VpIkt+djVFPuy16lvmvAqqdxXgCC47x5fxKfTBDm+CNo/j w==; X-IronPort-AV: E=McAfee;i="6500,9779,10548"; a="296050720" X-IronPort-AV: E=Sophos;i="5.96,209,1665471600"; d="scan'208";a="296050720" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Dec 2022 06:04:48 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10548"; a="750816643" X-IronPort-AV: E=Sophos;i="5.96,209,1665471600"; d="scan'208";a="750816643" Received: from mdechene-mobl2.amr.corp.intel.com (HELO [10.209.18.63]) ([10.209.18.63]) by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Dec 2022 06:04:46 -0800 Message-ID: <05148d42-2573-2b2d-2906-b7480ec21966@intel.com> Date: Thu, 1 Dec 2022 06:04:45 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: [tip: x86/fpu] x86/fpu/xstate: Define new functions for clearing fpregs and xstates Content-Language: en-US To: Ivan Zahariev , Thomas Gleixner , "Yu, Yu-cheng" , Andy Lutomirski , LKML Cc: linux-tip-commits@vger.kernel.org, Fenghua Yu , Borislav Petkov , Dave Hansen , Tony Luck , x86 , "Shankar, Ravi V" References: <20200512145444.15483-6-yu-cheng.yu@intel.com> <158964181793.17951.15480349640697746223.tip-bot2@tip-bot2> <10a553a5-699f-6921-705e-9afa1a8e42de@intel.com> <87y2c28zir.ffs@nanos.tec.linutronix.de> <31b30c00-9de9-2881-53c3-b08804571d6c@intel.com> <212daa8e-8f48-30d9-cfc8-ee5c2025f02c@icdsoft.com> From: Dave Hansen In-Reply-To: <212daa8e-8f48-30d9-cfc8-ee5c2025f02c@icdsoft.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/1/22 04:58, Ivan Zahariev wrote: > We are running 5.15.75 (LTS) but the problem started when we upgraded > from 5.15.31 to 5.15.59 and is present ever since. I erroneously said > that it's present into every 5.15. > I didn't do my homework well and blamed the commit by Yu-cheng Yu. > But this commit never landed into 5.15, nor the fix commit that you> > referred. There are no functions fpu__clear_all(), > copy_init_fpstate_to_fpregs(), copy_user_to_xstate() anywhere in the> > sources of 5.15.75 or 5.15.31, so the 5.15 kernel is running with a > different FPU implementation. It's also possible that the Ubuntu kernel folks pulled some FPU patches into their 5.15 kernel from later upstream kernels, which is adding to the confusion. I think there may have been some effort to backport the AMX work. You might want to file a bug report with the Ubuntu folks.