From: Dave Hansen <dave.hansen@intel.com>
To: Adamos Ttofari <attofari@amazon.de>
Cc: abusse@amazon.de, dwmw@amazon.co.uk, hborghor@amazon.de,
sironi@amazon.de, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Kyle Huey <me@kylehuey.com>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fpu: xstate: Keep xfd_state always in-sync with IA32_XFD MSR
Date: Thu, 11 May 2023 10:59:08 -0700 [thread overview]
Message-ID: <9f6ed500-fa60-c898-69fd-41ae4a401eb4@intel.com> (raw)
In-Reply-To: <20230511152818.13839-1-attofari@amazon.de>
On 5/11/23 08:28, Adamos Ttofari wrote:
> @@ -179,8 +179,14 @@ void fpu__init_cpu_xstate(void)
> * key as that does not work on the boot CPU. This also ensures
> * that any stale state is wiped out from XFD.
> */
> - if (cpu_feature_enabled(X86_FEATURE_XFD))
> - wrmsrl(MSR_IA32_XFD, init_fpstate.xfd);
> + if (cpu_feature_enabled(X86_FEATURE_XFD)) {
> + u64 xfd;
> +
> + rdmsrl(MSR_IA32_XFD, xfd);
> + __this_cpu_write(xfd_state, xfd);
> +
> + xfd_update_state(&init_fpstate);
> + }
The above comment didn't _quite_ make it into the context, so I'll paste
it here for your convenience:
> /*
> * Must happen after CR4 setup and before xsetbv() to allow KVM
> * lazy passthrough. Write independent of the dynamic state static
> * key as that does not work on the boot CPU. This also ensures
> * that any stale state is wiped out from XFD.
> */
Translating there, "the dynamic state static key" means
'__fpu_state_size_dynamic' which is used here:
> static __always_inline __pure bool fpu_state_size_dynamic(void)
> {
> return static_branch_unlikely(&__fpu_state_size_dynamic);
> }
You might recognize fpu_state_size_dynamic() from the first line of
xfd_update_state(), the function that you added to the above hunk.
Which brings me to ask what the point of calling xfd_update_state() is
in the first place if you're getting away with it not working on the
boot CPU.
Why not just short-circuit the (non-working) xfd_update_state() and do
this directly:
wrmsrl(MSR_IA32_XFD, init_fpstate.xfd);
__this_cpu_write(xfd_state, init_fpstate.xfd);
I don't think you even need to *READ* the MSR. You're going to blow it
away anyway.
> /*
> * XCR_XFEATURE_ENABLED_MASK (aka. XCR0) sets user features
> @@ -915,7 +921,7 @@ void fpu__resume_cpu(void)
> }
>
> if (fpu_state_size_dynamic())
> - wrmsrl(MSR_IA32_XFD, current->thread.fpu.fpstate->xfd);
> + xfd_update_state(&init_fpstate);
> }
>
> /*
next prev parent reply other threads:[~2023-05-11 18:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 15:28 Adamos Ttofari
2023-05-11 17:59 ` Dave Hansen [this message]
2023-05-11 19:11 ` Thomas Gleixner
2023-05-12 17:46 ` Chang S. Bae
2023-05-12 11:38 ` [PATCH v2] x86: fpu: Keep xfd_state always in sync with MSR_IA32_XFD Adamos Ttofari
2023-05-12 12:52 ` Thomas Gleixner
2023-05-19 11:23 ` [PATCH v3] " Adamos Ttofari
2023-05-19 15:03 ` Thomas Gleixner
2023-05-19 22:21 ` Chang S. Bae
2023-06-03 15:24 ` [PATCH] selftests/x86/amx: Add a CPU hotplug test Chang S. Bae
2024-03-22 23:04 ` [PATCH v4] x86/fpu: Keep xfd_state always in sync with MSR_IA32_XFD Chang S. Bae
2024-03-24 3:15 ` [tip: x86/urgent] x86/fpu: Keep xfd_state " tip-bot2 for Adamos Ttofari
2023-05-16 21:35 ` [PATCH v2] x86: fpu: Keep xfd_state always " 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=9f6ed500-fa60-c898-69fd-41ae4a401eb4@intel.com \
--to=dave.hansen@intel.com \
--cc=abusse@amazon.de \
--cc=andrew.cooper3@citrix.com \
--cc=attofari@amazon.de \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--cc=hborghor@amazon.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@kylehuey.com \
--cc=mingo@redhat.com \
--cc=sironi@amazon.de \
--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®