From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Dave Hansen <dave.hansen@intel.com>, <linux-kernel@vger.kernel.org>
Cc: <x86@kernel.org>, <platform-driver-x86@vger.kernel.org>,
<tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>, <hdegoede@redhat.com>,
<ilpo.jarvinen@linux.intel.com>, <tony.luck@intel.com>,
<ashok.raj@intel.com>, <jithu.joseph@intel.com>
Subject: Re: [PATCH v2 1/2] x86/fpu: Extend kernel_fpu_begin_mask() to initialize AMX state
Date: Thu, 9 May 2024 11:41:23 -0700 [thread overview]
Message-ID: <758089a4-52d5-4649-8aee-89e60044918a@intel.com> (raw)
In-Reply-To: <fde6149c-7ddf-488f-98c0-04f336b7092e@intel.com>
On 5/9/2024 10:36 AM, Dave Hansen wrote:
>
> I'd probably just do this:
>
> + kernel_fpu_begin();
> + // AMX *MUST* be in the init state for the wrmsr() to work.
> + // But, the more in the init state, the less state the test
> + // has to save and restore. Just zap everything.
> + restore_fpregs_from_fpstate(&init_fpstate,
> + fpu_user_cfg.max_features);
> +
I assume that this snippet goes to the IFS driver side. Then, we need to
introduce and export a new wrapper for this.
restore_fpregs_from_fpstate() and its arguments are not accessible as of
now.
Also, I think we should encapsulate them. If we follow this style, we
could have invoked tilerelease() directly from the idle driver, right?
> wrmsrl(MSR_ACTIVATE_SCAN, params->activate->data);
> rdmsrl(MSR_SCAN_STATUS, status.data);
>
> + kernel_fpu_end();
next prev parent reply other threads:[~2024-05-09 18:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 21:25 [PATCH 0/2] x86/fpu: Extend kernel_fpu_begin_mask() for the In-Field Scan driver Chang S. Bae
2024-04-30 21:25 ` [PATCH 1/2] x86/fpu: Extend kernel_fpu_begin_mask() to initialize AMX state Chang S. Bae
2024-04-30 23:42 ` Ashok Raj
2024-04-30 21:25 ` [PATCH 2/2] platform/x86/intel/ifs: Initialize AMX state for the scan test Chang S. Bae
2024-05-01 0:06 ` Ashok Raj
2024-05-01 8:58 ` Hans de Goede
2024-05-08 0:22 ` Chang S. Bae
2024-05-02 11:00 ` Ilpo Järvinen
2024-05-02 22:19 ` Chang S. Bae
2024-05-09 0:45 ` Kuppuswamy Sathyanarayanan
2024-05-02 20:52 ` [PATCH 0/2] x86/fpu: Extend kernel_fpu_begin_mask() for the In-Field Scan driver Chang S. Bae
2024-05-02 21:35 ` Chang S. Bae
2024-05-02 20:59 ` Dave Hansen
2024-05-07 23:53 ` [PATCH v2 " Chang S. Bae
2024-05-07 23:53 ` [PATCH v2 1/2] x86/fpu: Extend kernel_fpu_begin_mask() to initialize AMX state Chang S. Bae
2024-05-08 13:00 ` Thomas Gleixner
2024-05-08 14:40 ` Dave Hansen
2024-05-08 18:03 ` Chang S. Bae
2024-05-08 19:11 ` Dave Hansen
2024-05-09 0:29 ` Chang S. Bae
2024-05-09 17:36 ` Dave Hansen
2024-05-09 17:41 ` Dave Hansen
2024-05-09 18:41 ` Chang S. Bae [this message]
2024-05-09 18:50 ` Dave Hansen
2024-05-10 7:51 ` Thomas Gleixner
2024-05-07 23:53 ` [PATCH v2 2/2] platform/x86/intel/ifs: Initialize AMX state for the scan test Chang S. Bae
2024-05-08 0:19 ` Ashok Raj
2024-05-08 0:21 ` Chang S. Bae
2024-05-08 8:28 ` [PATCH v2 0/2] x86/fpu: Extend kernel_fpu_begin_mask() for the In-Field Scan driver Ilpo Järvinen
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=758089a4-52d5-4649-8aee-89e60044918a@intel.com \
--to=chang.seok.bae@intel.com \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jithu.joseph@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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