From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<linux-pm@vger.kernel.org>
Cc: <dave.hansen@linux.intel.com>, <peterz@infradead.org>,
<bp@alien8.de>, <rafael@kernel.org>, <ravi.v.shankar@intel.com>
Subject: Re: [PATCH v3 2/3] x86/fpu: Add a helper to prepare AMX state for low-power CPU idle
Date: Mon, 4 Apr 2022 17:24:06 -0700 [thread overview]
Message-ID: <a4a46d80-d3b2-9e08-c80d-ab72298931f9@intel.com> (raw)
In-Reply-To: <8735ium8bv.ffs@tglx>
On 4/3/2022 9:37 AM, Thomas Gleixner wrote:
> On Thu, Mar 24 2022 at 19:22, Chang S. Bae wrote:
>> When a CPU enters an idle state, non-initialized states left in large
>> registers may be the cause of preventing deeper low-power states.
>>
>> The new helper ensures the AMX state is initialized to make the CPU
>> ready for low-power states. It will be used by the intel idle driver.
>
> What about AVX...AVX512? Are they harmless in that regard?
I double-checked with HW folks. Yes, that's the case. Their state
whether initialized or not does not prevent the processor from entering
a deeper low-power state.
>
> If so, then the first sentence above is confusing and should clearly
> spell out that it's AMX which causes that problem.
I see. Will do that.
Thanks,
Chang
next prev parent reply other threads:[~2022-04-05 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 2:22 [PATCH v3 0/3] x86/fpu: Make AMX state ready for " Chang S. Bae
2022-03-25 2:22 ` [PATCH v3 1/3] x86/fpu: Make XCR0 accessors immune to unwanted compiler reordering Chang S. Bae
2022-04-01 17:58 ` Dave Hansen
2022-04-01 18:16 ` Dave Hansen
2022-04-01 22:14 ` Chang S. Bae
2022-03-25 2:22 ` [PATCH v3 2/3] x86/fpu: Add a helper to prepare AMX state for low-power CPU idle Chang S. Bae
2022-04-03 16:37 ` Thomas Gleixner
2022-04-05 0:24 ` Chang S. Bae [this message]
2022-03-25 2:22 ` [PATCH v3 3/3] intel_idle: Add a new flag to initialize the AMX state Chang S. Bae
2022-03-29 17:42 ` Rafael J. Wysocki
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=a4a46d80-d3b2-9e08-c80d-ab72298931f9@intel.com \
--to=chang.seok.bae@intel.com \
--cc=bp@alien8.de \
--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
all inboxes | Powered by JetHome®