Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: David Laight <david.laight.linux@gmail.com>
Cc: x86@kernel.org, linux-um@lists.infradead.org,
	linux-raid@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2 3/8] crypto: x86 - Stop using cpu_has_xfeatures()
Date: Tue, 28 Jul 2026 16:40:25 -0700	[thread overview]
Message-ID: <20260728234025.GB3277@quark> (raw)
In-Reply-To: <20260728103018.00938ac6@pumpkin>

On Tue, Jul 28, 2026 at 10:30:18AM +0100, David Laight wrote:
> On Mon, 27 Jul 2026 19:15:58 -0700
> Eric Biggers <ebiggers@kernel.org> wrote:
> 
> > Checking both boot_cpu_has(X86_FEATURE_AVX*) and cpu_has_xfeatures() has
> > never really been needed in practice, and it's never been universally
> > done (e.g., lib/raid/ omits cpu_has_xfeatures()).  Nevertheless, both
> > x86 and UML now explicitly clear the AVX and AVX-512 flags if their
> > xfeatures are missing, which should remove any remaining doubts.
> > 
> > Thus, remove all the calls to cpu_has_xfeatures(), as well as the
> > related checks of boot_cpu_has(X86_FEATURE_OSXSAVE).
> > 
> > In a few cases there was no corresponding boot_cpu_has(X86_FEATURE_AVX*)
> > check, so add the missing ones.
> > 
> > Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> > ---
> ...
> > --- a/arch/x86/crypto/aria_gfni_avx512_glue.c
> > +++ b/arch/x86/crypto/aria_gfni_avx512_glue.c
> > @@ -196,24 +196,15 @@ static struct skcipher_alg aria_algs[] = {
> >  
> >  static int __init aria_avx512_init(void)
> >  {
> > -	const char *feature_name;
> > -
> >  	if (!boot_cpu_has(X86_FEATURE_AVX) ||
> >  	    !boot_cpu_has(X86_FEATURE_AVX2) ||
> 
> Doesn't AVX2 require AVX support?
> 
> >  	    !boot_cpu_has(X86_FEATURE_AVX512F) ||
> >  	    !boot_cpu_has(X86_FEATURE_AVX512VL) ||
> 
> And (less sure) AVX512xxx require AVX2?
> 
> So the extra checks could be reduced.

Yes, but this patch is just intended to clean up the xfeatures and
OSXSAVE checks.  Further cleanups would be separate patches.

- Eric

  reply	other threads:[~2026-07-28 23:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28  2:15 [PATCH v2 0/8] x86: Remove cpu_has_xfeatures() and add AVX-512 xor_gen() Eric Biggers
2026-07-28  2:15 ` [PATCH v2 1/8] x86/fpu: Check for missing AVX and AVX-512 xstate bits Eric Biggers
2026-07-28  5:27   ` Borislav Petkov
2026-07-28  5:45     ` Eric Biggers
2026-07-28 18:20       ` Borislav Petkov
2026-07-28 18:34         ` Eric Biggers
2026-07-28 22:59           ` Borislav Petkov
2026-07-28 23:34             ` Eric Biggers
2026-07-28 23:47               ` Borislav Petkov
2026-07-28  9:23     ` David Laight
2026-07-28 22:35   ` Thomas Gleixner
2026-07-28  2:15 ` [PATCH v2 2/8] um: " Eric Biggers
2026-07-28  2:15 ` [PATCH v2 3/8] crypto: x86 - Stop using cpu_has_xfeatures() Eric Biggers
2026-07-28  9:30   ` David Laight
2026-07-28 23:40     ` Eric Biggers [this message]
2026-07-28  2:15 ` [PATCH v2 4/8] lib/crypto: x86: " Eric Biggers
2026-07-28  2:16 ` [PATCH v2 5/8] lib/crc: " Eric Biggers
2026-07-28  2:16 ` [PATCH v2 6/8] x86/fpu: Remove cpu_has_xfeatures() Eric Biggers
2026-07-28  2:16 ` [PATCH v2 7/8] lib/raid/xor: x86: Remove redundant X86_FEATURE_OSXSAVE check Eric Biggers
2026-07-28  3:41   ` Christoph Hellwig
2026-07-28  2:16 ` [PATCH v2 8/8] lib/raid/xor: x86: Add AVX-512 optimized xor_gen() Eric Biggers
2026-07-28  3:44   ` Christoph Hellwig
2026-07-28  3:44 ` [PATCH v2 0/8] x86: Remove cpu_has_xfeatures() and add AVX-512 xor_gen() Christoph Hellwig

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=20260728234025.GB3277@quark \
    --to=ebiggers@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=david.laight.linux@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --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