From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org
Cc: Dave Hansen <dave.hansen@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 0/2] x86/fpu: Clean up "dynamic" APIs
Date: Thu, 10 Jun 2021 22:13:35 -0700 [thread overview]
Message-ID: <cover.1623388344.git.luto@kernel.org> (raw)
"Dynamic" XSTATEs are not dynamic. They are just managed separately from
the normal struct fpu states. Rename the functions and make their interfaces
sane.
Andy Lutomirski (2):
x86/fpu: Rename "dynamic" XSTATEs to "independent"
x86/fpu: Improve FPU APIs for independent features
arch/x86/events/intel/lbr.c | 6 +--
arch/x86/include/asm/fpu/xstate.h | 19 +++++----
arch/x86/kernel/fpu/core.c | 3 ++
arch/x86/kernel/fpu/xstate.c | 67 +++++++++++++------------------
4 files changed, 46 insertions(+), 49 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-11 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 5:13 Andy Lutomirski [this message]
2021-06-11 5:13 ` [PATCH 1/2] x86/fpu: Rename "dynamic" XSTATEs to "independent" Andy Lutomirski
2021-06-11 8:01 ` Peter Zijlstra
2021-06-11 13:30 ` Thomas Gleixner
2021-06-23 22:09 ` [tip: x86/fpu] " tip-bot2 for Andy Lutomirski
2021-06-11 5:13 ` [PATCH 2/2] x86/fpu: Improve FPU APIs for independent features Andy Lutomirski
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=cover.1623388344.git.luto@kernel.org \
--to=luto@kernel.org \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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