From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Dave Hansen <dave.hansen@intel.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<linux-pm@vger.kernel.org>
Cc: <tglx@linutronix.de>, <dave.hansen@linux.intel.com>,
<peterz@infradead.org>, <bp@alien8.de>, <rafael@kernel.org>,
<ravi.v.shankar@intel.com>
Subject: Re: [PATCH v2 1/2] x86/fpu: Add a helper to prepare AMX state for low-power CPU idle
Date: Thu, 10 Mar 2022 13:00:56 -0800 [thread overview]
Message-ID: <13346402-7580-d60e-bb88-3172dd60406f@intel.com> (raw)
In-Reply-To: <4331a0af-2300-ffaa-3e5c-ed15499c213b@intel.com>
On 3/9/2022 4:24 PM, Dave Hansen wrote:
>
> I assume that splat is because 0day found a CPU which doesn't support
> XGETBV1. Since fpu_state_size_dynamic() only ever returns true on
> XGETBV1 systems so it works as a proxy for checking XGETBV1 support.
>
> Right? >
> If so, then fpu_state_size_dynamic() is a *bit* of an oblique way to
> check for XGETBV1 support.
> > Why don't we do a good old:
>
> cpu_feature_enabled(X86_FEATURE_XGETBV1)
>
> check?
Agreed, checking XGETBV1 support is the reason for this, so this looks
to be straightforward here.
>
> Also, did we get the asm constraints wrong on xgetbv()? Surely we
> shouldn't be allowing the compiler to reorder it. Do we need a "memory"
> constraint?
I think this is a good point. Perhaps x{get|set}bv() may follow this
change [1] to prevent any reordering.
BTW, now I'm suspicious of this JMP as patched at runtime with
fpu_state_size_dynamic():
22: eb 01 jmp 0x25
24: c3 retq
25: b9 01 00 00 00 mov $0x1,%ecx
2a:* 0f 01 d0 xgetbv <-- trapping instruction
Still, the question is, if so, why it was patched on non-XFD systems.
Let me analyze the case a bit further with 0day folks.
Thanks,
Chang
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa5cacdc29d76a005cbbee018a47faa6e724dd2d
next prev parent reply other threads:[~2022-03-10 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 22:34 [PATCH v2 0/2] x86/fpu: Make AMX state ready for CPU idle Chang S. Bae
2022-03-09 22:34 ` [PATCH v2 1/2] x86/fpu: Add a helper to prepare AMX state for low-power " Chang S. Bae
2022-03-09 22:46 ` Dave Hansen
2022-03-09 23:12 ` Chang S. Bae
2022-03-10 0:24 ` Dave Hansen
2022-03-10 21:00 ` Chang S. Bae [this message]
2022-03-22 7:05 ` Chang S. Bae
2022-03-09 22:34 ` [PATCH v2 2/2] intel_idle: Add a new flag to initialize the AMX state Chang S. Bae
2022-03-10 18:34 ` Rafael J. Wysocki
2022-03-10 18:50 ` Chang S. Bae
2022-03-11 7:33 ` Artem Bityutskiy
2022-03-22 7:06 ` 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=13346402-7580-d60e-bb88-3172dd60406f@intel.com \
--to=chang.seok.bae@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=ravi.v.shankar@intel.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