From: Eric Biggers <ebiggers@kernel.org>
To: Borislav Petkov <bp@alien8.de>
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 v3 0/8] x86: Remove cpu_has_xfeatures() and add AVX-512 xor_gen()
Date: Fri, 14 Aug 2026 19:59:39 +0000 [thread overview]
Message-ID: <20260814195939.GB2644249@google.com> (raw)
In-Reply-To: <20260814003517.GBan5ixaTArd0Sf6X3@fat_crate.local>
On Thu, Aug 13, 2026 at 05:35:17PM -0700, Borislav Petkov wrote:
> On Wed, Aug 12, 2026 at 07:14:58PM -0700, Eric Biggers wrote:
> > This series consolidates and cleans up how the kernel handles CPU
> > feature flags for AVX and AVX-512 when the underlying OS or hypervisor
> > (if any) doesn't enable the required xstate features in XCR0.
> >
> > Specifically, it makes the checks for xstate features be done in a
> > single place at boot time for both UML and native x86, instead of
> > everywhere kernel code wants to check for AVX or AVX-512 support.
> >
> > Patch 8 then adds an AVX-512 optimized implementation of xor_gen() for
> > RAID, which had been blocked on confusion around cpu_has_xfeatures() and
> > its lack of implementation on UML.
>
> Sashiko complains about a missing VZEROUPPER there in patch 8:
>
> https://sashiko.dev/#/patchset/20260813021506.55129-1-ebiggers%40kernel.org
Yeah, missing vzeroupper is a common mistake... All the other code in
lib/raid/ that uses ymm and zmm registers misses it too. I've fixed
various instances of this in the crypto code before, but no one ever
checked the RAID code. I guess I'll send out a v4 that fixes patch 8,
and also separate patches that try to fix all the existing instances of
missing vzeroupper. Besides lib/raid/, some also have slipped in in
arch/x86/crypto/aria-* and net/netfilter/nft_set_pipapo_avx2.c.
- Eric
prev parent reply other threads:[~2026-08-14 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 2:14 [PATCH v3 0/8] x86: Remove cpu_has_xfeatures() and add AVX-512 xor_gen() Eric Biggers
2026-08-13 2:14 ` [PATCH v3 1/8] x86/fpu: Check for missing AVX and AVX-512 xstate bits Eric Biggers
2026-08-13 2:15 ` [PATCH v3 2/8] um: " Eric Biggers
2026-08-13 2:15 ` [PATCH v3 3/8] crypto: x86 - Stop using cpu_has_xfeatures() Eric Biggers
2026-08-13 2:15 ` [PATCH v3 4/8] lib/crypto: x86: " Eric Biggers
2026-08-13 2:15 ` [PATCH v3 5/8] lib/crc: " Eric Biggers
2026-08-13 2:15 ` [PATCH v3 6/8] x86/fpu: Remove cpu_has_xfeatures() Eric Biggers
2026-08-13 2:15 ` [PATCH v3 7/8] xor: Remove redundant X86_FEATURE_OSXSAVE check Eric Biggers
2026-08-13 2:15 ` [PATCH v3 8/8] xor: Add AVX-512 optimized xor_gen() Eric Biggers
2026-08-14 0:35 ` [PATCH v3 0/8] x86: Remove cpu_has_xfeatures() and add AVX-512 xor_gen() Borislav Petkov
2026-08-14 19:59 ` Eric Biggers [this message]
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=20260814195939.GB2644249@google.com \
--to=ebiggers@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--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