mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
	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 v5 6/8] x86/fpu: Remove cpu_has_xfeatures()
Date: Thu, 10 Sep 2026 09:59:33 -0500	[thread overview]
Message-ID: <20260910145933.GB5719@quark> (raw)
In-Reply-To: <20260910142301.GAaqK9RVdjjmpwX876@fat_crate.local>

On Thu, Sep 10, 2026 at 07:23:01AM -0700, Borislav Petkov wrote:
> On Thu, Sep 10, 2026 at 10:38:01AM +0200, Peter Zijlstra wrote:
> > Boris, can you have a look? For now I'm reverting this patch locally.
> 
> Yeah, I'll zap it from the x86/fpu lineup and then we can see how to fix up
> everything later.

How about just applying patches 1-5 and 7-8, and deferring the actual
removal of cpu_has_xfeatures() to the next cycle?

> I'm not entirely sure how to go about fixing this. Some seem trivial
> enough, but others, like XFEATURE_MASK_OPMASK I don't readily see a
> replacement for.

XFEATURE_MASK_OPMASK is just part of the AVX-512 state and it will be
implied by X86_FEATURE_AVX512F.

- Eric

  reply	other threads:[~2026-09-10 14:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 14:57 [PATCH v5 0/8] x86: Remove cpu_has_xfeatures() and add AVX-512 xor_gen() Eric Biggers
2026-09-01 14:57 ` [PATCH v5 1/8] x86/fpu: Check for missing AVX and AVX-512 xstate bits Eric Biggers
2026-09-09 23:58   ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-01 14:57 ` [PATCH v5 2/8] um: " Eric Biggers
2026-09-09 23:58   ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-01 14:57 ` [PATCH v5 3/8] crypto: x86 - Stop using cpu_has_xfeatures() Eric Biggers
2026-09-09 23:58   ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-01 14:57 ` [PATCH v5 4/8] lib/crypto: x86: " Eric Biggers
2026-09-09 23:57   ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-01 14:57 ` [PATCH v5 5/8] lib/crc: " Eric Biggers
2026-09-09 23:57   ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-01 14:57 ` [PATCH v5 6/8] x86/fpu: Remove cpu_has_xfeatures() Eric Biggers
2026-09-09 23:57   ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-10  8:38   ` [PATCH v5 6/8] " Peter Zijlstra
2026-09-10 14:23     ` Borislav Petkov
2026-09-10 14:59       ` Eric Biggers [this message]
2026-09-10 15:44         ` Borislav Petkov
2026-09-01 14:57 ` [PATCH v5 7/8] xor: Remove redundant X86_FEATURE_OSXSAVE check Eric Biggers
2026-09-09 23:57   ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-10 15:38   ` tip-bot2 for Eric Biggers
2026-09-01 14:57 ` [PATCH v5 8/8] xor: Add AVX-512 optimized xor_gen() Eric Biggers
2026-09-09 23:57   ` [tip: x86/fpu] " tip-bot2 for Eric Biggers
2026-09-10 15:38   ` tip-bot2 for Eric Biggers
2026-09-02 17:11 ` [PATCH v5 0/8] x86: Remove cpu_has_xfeatures() and add AVX-512 xor_gen() Borislav Petkov

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=20260910145933.GB5719@quark \
    --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=peterz@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

all inboxes | Powered by JetHome®