From: Dave Hansen <dave.hansen@intel.com>
To: Ivan Zahariev <famzah@icdsoft.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Yu, Yu-cheng" <yu-cheng.yu@intel.com>,
Andy Lutomirski <luto@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: linux-tip-commits@vger.kernel.org,
Fenghua Yu <fenghua.yu@intel.com>, Borislav Petkov <bp@suse.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Tony Luck <tony.luck@intel.com>, x86 <x86@kernel.org>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>
Subject: Re: [tip: x86/fpu] x86/fpu/xstate: Define new functions for clearing fpregs and xstates
Date: Thu, 1 Dec 2022 06:04:45 -0800 [thread overview]
Message-ID: <05148d42-2573-2b2d-2906-b7480ec21966@intel.com> (raw)
In-Reply-To: <212daa8e-8f48-30d9-cfc8-ee5c2025f02c@icdsoft.com>
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.
next prev parent reply other threads:[~2022-12-01 14:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 14:54 [PATCH v4 00/10] Support XSAVES supervisor states Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 01/10] x86/fpu/xstate: Rename validate_xstate_header() to validate_user_xstate_header() Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Fenghua Yu
2020-05-12 14:54 ` [PATCH v4 02/10] x86/fpu/xstate: Define new macros for supervisor and user xstates Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Fenghua Yu
2020-05-12 14:54 ` [PATCH v4 03/10] x86/fpu/xstate: Separate user and supervisor xfeatures mask Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 04/10] x86/fpu/xstate: Introduce XSAVES supervisor states Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 05/10] x86/fpu/xstate: Define new functions for clearing fpregs and xstates Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Fenghua Yu
2021-05-24 16:34 ` Andy Lutomirski
2021-05-25 17:44 ` Yu, Yu-cheng
2021-05-25 18:00 ` Thomas Gleixner
2022-11-29 11:19 ` Ivan Zahariev
2022-11-29 18:16 ` Dave Hansen
2022-12-01 12:58 ` Ivan Zahariev
2022-12-01 14:04 ` Dave Hansen [this message]
2020-05-12 14:54 ` [PATCH v4 06/10] x86/fpu/xstate: Update sanitize_restored_xstate() for supervisor xstates Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 07/10] x86/fpu/xstate: Update copy_kernel_to_xregs_err() for XSAVES supervisor states Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] x86/fpu/xstate: Update copy_kernel_to_xregs_err() for " tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 08/10] x86/fpu: Introduce copy_supervisor_to_kernel() Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 09/10] x86/fpu/xstate: Preserve supervisor states for slow path of __fpu__restore_sig() Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] x86/fpu/xstate: Preserve supervisor states for the slow path in __fpu__restore_sig() tip-bot2 for Yu-cheng Yu
2020-05-12 14:54 ` [PATCH v4 10/10] x86/fpu/xstate: Restore supervisor states for signal return Yu-cheng Yu
2020-05-16 15:10 ` [tip: x86/fpu] " tip-bot2 for Yu-cheng Yu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=05148d42-2573-2b2d-2906-b7480ec21966@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=famzah@icdsoft.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@kernel.org \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®