From: Borislav Petkov <bp@alien8.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
x86@kernel.org, linux-block@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>, Keith Busch <kbusch@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH v4 1/6] x86: move ZMM exclusion list into CPU feature flag
Date: Mon, 10 Feb 2025 22:49:13 +0100 [thread overview]
Message-ID: <20250210214913.GDZ6p0WdZL259TOMa7@fat_crate.local> (raw)
In-Reply-To: <20250210213705.GD348261@sol.localdomain>
On Mon, Feb 10, 2025 at 01:37:05PM -0800, Eric Biggers wrote:
> I'll also note that boot_cpu_has() is missing a comment that says it is
> deprecated (if it really is).
/*
* This is the default CPU features testing macro to use in code.
^^^^^^^^^^^^^
*
* It is for detection of features which need kernel infrastructure to be
* used. It may *not* directly test the CPU itself. Use the cpu_has() family
* if you want true runtime testing of CPU features, like in hypervisor code
* where you are supporting a possible guest feature where host support for it
* is not relevant.
*/
#define cpu_feature_enabled(bit) \
(__builtin_constant_p(bit) && DISABLED_MASK_BIT_SET(bit) ? 0 : static_cpu_has(bit))
#define boot_cpu_has(bit) cpu_has(&boot_cpu_data, bit)
---
Forget what I said - we'll convert everything when the time comes.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2025-02-10 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 17:45 [PATCH v4 0/6] x86 CRC optimizations Eric Biggers
2025-02-10 17:45 ` [PATCH v4 1/6] x86: move ZMM exclusion list into CPU feature flag Eric Biggers
2025-02-10 20:40 ` Borislav Petkov
2025-02-10 21:01 ` Eric Biggers
2025-02-10 21:17 ` Borislav Petkov
2025-02-10 21:37 ` Eric Biggers
2025-02-10 21:49 ` Borislav Petkov [this message]
2025-02-10 17:45 ` [PATCH v4 2/6] scripts/gen-crc-consts: add gen-crc-consts.py Eric Biggers
2025-02-10 17:45 ` [PATCH v4 3/6] x86/crc: add "template" for [V]PCLMULQDQ based CRC functions Eric Biggers
2025-02-10 17:45 ` [PATCH v4 4/6] x86/crc32: implement crc32_le using new template Eric Biggers
2025-02-10 17:45 ` [PATCH v4 5/6] x86/crc-t10dif: implement crc_t10dif " Eric Biggers
2025-02-10 17:45 ` [PATCH v4 6/6] x86/crc64: implement crc64_be and crc64_nvme " Eric Biggers
2025-02-10 18:01 ` [PATCH v4 0/6] x86 CRC optimizations Eric Biggers
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=20250210214913.GDZ6p0WdZL259TOMa7@fat_crate.local \
--to=bp@alien8.de \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=kbusch@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mingo@kernel.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®