mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Chang S. Bae" <chang.seok.bae@intel.com>
Cc: LKML <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,  Hans de Goede <hdegoede@redhat.com>,
	tony.luck@intel.com,  ashok.raj@intel.com,
	jithu.joseph@intel.com,
	 sathyanarayanan.kuppuswamy@linux.intel.com
Subject: Re: [PATCH v3 0/3] x86/fpu: Allow the In-Field Scan driver to initialize FPU state
Date: Mon, 3 Jun 2024 13:11:16 +0300 (EEST)	[thread overview]
Message-ID: <676bfc09-c1f4-9272-a198-3fb865868c10@linux.intel.com> (raw)
In-Reply-To: <20240530192739.172566-1-chang.seok.bae@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1391 bytes --]

On Thu, 30 May 2024, Chang S. Bae wrote:

> This revision switches to a new approach by providing a helper to
> initialize user FPU states for the driver, which is considerably simpler.
> This approach could serve as an example for addressing similar situations
> from a non-critical path.
> 
> I thought fpu_reset_fpregs() as the helper name. There is already one
> with this name. Then, I realized the existing one is a bit misaligned, so
> renamed it first here.
> 
> Thanks to Dave for the reviews and the suggestion.
> 
> Thanks,
> Chang
> 
> The previous postings:
> V2: https://lore.kernel.org/all/20240507235344.249103-1-chang.seok.bae@intel.com
> V1: https://lore.kernel.org/all/20240430212508.105117-1-chang.seok.bae@intel.com
> 
> Chang S. Bae (3):
>   x86/fpu: Rename fpu_reset_fpregs() to fpu_reset_fpstate_regs()
>   x86/fpu: Allow FPU users to initialize FPU state
>   platform/x86/intel/ifs: Initialize FPU states for the scan test
> 
>  arch/x86/include/asm/fpu/api.h           |  2 ++
>  arch/x86/kernel/fpu/core.c               | 17 ++++++++++++++---
>  drivers/platform/x86/intel/ifs/ifs.h     |  1 +
>  drivers/platform/x86/intel/ifs/runtest.c |  7 +++++++
>  4 files changed, 24 insertions(+), 3 deletions(-)

Acked-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>

Do x86 maintainers plan to take these through their tree?

-- 
 i.

  parent reply	other threads:[~2024-06-03 10:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 19:27 Chang S. Bae
2024-05-30 19:27 ` [PATCH v3 1/3] x86/fpu: Rename fpu_reset_fpregs() to fpu_reset_fpstate_regs() Chang S. Bae
2024-05-30 19:27 ` [PATCH v3 2/3] x86/fpu: Allow FPU users to initialize FPU state Chang S. Bae
2024-05-30 19:27 ` [PATCH v3 3/3] platform/x86/intel/ifs: Initialize FPU states for the scan test Chang S. Bae
2024-06-03 10:11 ` Ilpo Järvinen [this message]
2024-06-03 12:10   ` [PATCH v3 0/3] x86/fpu: Allow the In-Field Scan driver to initialize FPU state Dave Hansen

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=676bfc09-c1f4-9272-a198-3fb865868c10@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=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=jithu.joseph@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --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®