From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
avagin@gmail.com, seanjc@google.com, chang.seok.bae@intel.com
Subject: [PATCH v3 0/3] x86/fpu: Fix MXCSR handling and SSE component definition
Date: Wed, 5 Oct 2022 14:53:54 -0700 [thread overview]
Message-ID: <20221005215357.1808-1-chang.seok.bae@intel.com> (raw)
Hi all,
Changes from v2 [1]:
* Drop the changes in fpstate_clear_xstate_component().
* Massage the WARNING and the comment in xfeature_get_offset().
If the former function is called for any legacy state, the WARNING is
eventually emitted by the latter function in this call chain:
fpstate_clear_xstate_component()
-> get_xsave_addr()
-> __raw_xsave_addr()
-> xfeature_get_offset()
So, the change in the outer function (the old patch3) was considered as not
necessary.
Thanks Sean Christopherson for the feedback.
== Regression ==
Recently the XSTATE copy functions were unitized together [2]. At a glance,
this change appears to relapse the ptrace write on the MXCSR state when
the non-compacted format is used in the kernel.
But, this regression appears to root in the XSAVES-enabling code [3] that
introduced the XSTATE conversion along with the MXCSR mistreatment.
== MXCSR Hindsight ==
MXCSR is architecturally part of the SSE component. The MXCSR association
of XSTATE_BV depends on the XSAVE format.
The change [3], however, presumed MXCSR as part of the X87 component and
made the kernel referencing XSTATE_BV regardless of the format.
== Patches ==
* Fix the MXCSR conversion code along with adding the test case.
* The hard-coded legacy state offset and size are adjusted in the end. And
add a WARN when they are referenced.
These patches can be also found in this repository:
git://github.com/intel/amx-linux.git mxcsr
Thanks,
Chang
[1] v2: https://lore.kernel.org/lkml/20220922200034.23759-1-chang.seok.bae@intel.com/
[2] Commit 43be46e89698 ("x86/fpu: Sanitize xstateregs_set()")
[3] Commit 91c3dba7dbc1 ("x86/fpu/xstate: Fix PTRACE frames for XSAVES")
Chang S. Bae (3):
x86/fpu: Fix the MXCSR state reshuffling between userspace and kernel
buffers
selftests/x86/mxcsr: Test the MXCSR state write via ptrace
x86/fpu: Correct the legacy state offset and size information
arch/x86/kernel/fpu/xstate.c | 89 ++++++++----
tools/testing/selftests/x86/Makefile | 2 +-
tools/testing/selftests/x86/mxcsr.c | 200 +++++++++++++++++++++++++++
3 files changed, 262 insertions(+), 29 deletions(-)
create mode 100644 tools/testing/selftests/x86/mxcsr.c
base-commit: 03c739a21613a1a85f730dd972ff928e573f7235
--
2.17.1
next reply other threads:[~2022-10-05 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 21:53 Chang S. Bae [this message]
2022-10-05 21:53 ` [PATCH v3 1/3] x86/fpu: Fix the MXCSR state reshuffling between userspace and kernel buffers Chang S. Bae
2022-10-05 21:53 ` [PATCH v3 2/3] selftests/x86/mxcsr: Test the MXCSR state write via ptrace Chang S. Bae
2022-10-05 21:53 ` [PATCH v3 3/3] x86/fpu: Correct the legacy state offset and size information Chang S. Bae
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=20221005215357.1808-1-chang.seok.bae@intel.com \
--to=chang.seok.bae@intel.com \
--cc=avagin@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®