From: Ashok Raj <ashok.raj@intel.com>
To: "Chang S. Bae" <chang.seok.bae@intel.com>
Cc: <linux-kernel@vger.kernel.org>, <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>, <jithu.joseph@intel.com>,
Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCH v2 2/2] platform/x86/intel/ifs: Initialize AMX state for the scan test
Date: Tue, 7 May 2024 17:19:07 -0700 [thread overview]
Message-ID: <ZjrE+6UEhKFFYvBG@a4bf019067fa.jf.intel.com> (raw)
In-Reply-To: <20240507235344.249103-3-chang.seok.bae@intel.com>
On Tue, May 07, 2024 at 04:53:44PM -0700, Bae, Chang Seok wrote:
> In-Field Scan aborts if AMX state is not in initialized state. Use
> kernel_fpu_begin_mask(KFPU_AMX) to ensure AMX state is initialized.
>
> Introduce custom FPU handling wrappers to ensure compliance with the
> established FPU API semantics. This change follows the EFI case from
> commit b0dc553cfc9d ("x86/fpu: Make the EFI FPU calling convention
> explicit").
>
> Then, use these wrappers to surround the MSR_ACTIVATE_SCAN write to
> minimize the critical section. To prevent unnecessary delays, invoke
> ifs_fpu_begin() before entering the rendezvous loop.
>
> Signed-off-by: Chang S. Bae <chang.seok.bae@intel.com>
> Reviewed-by: Jithu Joseph <jithu.joseph@intel.com>
> Tested-by: Jithu Joseph <jithu.joseph@intel.com>
> Acked-by: Hans de Goede <hdegoede@redhat.com>
Reviewed-by: Ashok Raj <ashok.raj@intel.com>
for both patches.
next prev parent reply other threads:[~2024-05-08 0:19 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
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 [this message]
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=ZjrE+6UEhKFFYvBG@a4bf019067fa.jf.intel.com \
--to=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@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
all inboxes | Powered by JetHome®