zstd: probe the CPU for BMI2 support once, not per context
Subsystems (2)
cover zstd: probe the CPU for BMI2 support once, not per context
zstd picks between BMI2 and generic code paths at runtime, and issues CPUID to decide every time a compression or decompression context is set up. The answer cannot change while the kernel is running.
It is not a cold path: squashfs calls zstd_init_dstream() for every block it decompresses, and erofs, btrfs, f2fs and crypto/zstd all initialise a context per operation. Each probe is two serializing CPUID instructions on x86.
Patch 1 routes ZSTD_initStaticCCtx() through ZSTD_cpuSupportsBmi2() instead of open-coding the probe, which also fixes it testing for BMI2 without BMI1 - the bodies it selects are tagged TARGET_ATTRIBUTE("lzcnt,bmi,bmi2"), so both are needed. No CPU in the field implements BMI2 without BMI1, so this is latent. Patch 2 skips the probe when DYNAMIC_BMI2 is 0, where every consumer ignores the flag anyway. Patch 3 caches the result.
A 4 KiB crypto_acomp benchmark [1] in a one-vCPU KVM guest, twelve boots of nine 30,000-operation rounds, median per-round mean over 108 rounds:
compress decompress
unpatched 16,756 ns 3,455 ns
patched 13,646 ns 1,002 ns
-3,110 ns -2,452 ns
(18.6%) (71.0%)The main reason is because CPUID is an unconditional VM exit.
[1] https://gist.github.com/uarif1/5cf02f0e22c23f0d1b3d84348f12914c
Usama Arif (3):
zstd: use ZSTD_cpuSupportsBmi2() in ZSTD_initStaticCCtx()
zstd: skip the BMI2 probe when dynamic BMI2 dispatch is disabled
zstd: probe the CPU for BMI2 support only once
lib/zstd/common/zstd_internal.h | 22 ++++++++++++++++++++-- lib/zstd/compress/zstd_compress.c | 2 +- 2 files changed, 21 insertions(+), 3 deletions(-)
base-commit: 4b18edbd8e70f7e6860d56370f13244896d0f95c
Signature · 1 line
2.53.0-Meta
PATCH 1/3 zstd: use ZSTD_cpuSupportsBmi2() in ZSTD_initStaticCCtx()
ZSTD_initStaticCCtx() open-codes its BMI2 probe as ZSTD_cpuid_bmi2(ZSTD_cpuid()). Every other context setup - ZSTD_initCCtx() and ZSTD_initDCtx_internal() - goes through ZSTD_cpuSupportsBmi2(), which requires BMI1 as well as BMI2.
Requiring both is the correct test. The alternate function bodies the flag selects are tagged BMI2_TARGET_ATTRIBUTE, which is TARGET_ATTRIBUTE("lzcnt,bmi,bmi2"), so the compiler may emit BMI1 and LZCNT instructions in them; BMI2 alone does not make that safe. No shipping x86 CPU implements BMI2 without BMI1, so this is a latent inconsistency rather than an observed failure.
Route the static path through the same helper. That also leaves a single place where the probe is issued, which the following patches build on.
No functional change on any CPU in the field.
--- lib/zstd/compress/zstd_compress.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
lib/zstd/compress/zstd_compress.c +1 -1
@@ -142,7 +142,7 @@ ZSTD_CCtx* ZSTD_initStaticCCtx(void* workspace, size_t workspaceSize) cctx->blockState.nextCBlock = (ZSTD_compressedBlockState_t *)ZSTD_cwksp_reserve_object (&cctx->workspace,sizeof (ZSTD_compressedBlockState_t)); cctx->tmpWorkspace =ZSTD_cwksp_reserve_object (&cctx->workspace,TMP_WORKSPACE_SIZE ); cctx->tmpWkspSize =TMP_WORKSPACE_SIZE ; - cctx->bmi2 =ZSTD_cpuid_bmi2 (ZSTD_cpuid ()); + cctx->bmi2 =ZSTD_cpuSupportsBmi2 ();return cctx; }
Signature · 1 line
2.53.0-Meta
PATCH 2/3 zstd: skip the BMI2 probe when dynamic BMI2 dispatch is disabled
In reply to Usama ArifWhen DYNAMIC_BMI2 is 0 - GCC older than 11, a non-x86 target, or a build that already has BMI2 on globally - nothing reads the flag. HUF_compress1X_usingCTable_internal(), FSE_decompress_wksp_bmi2(), HUF_readStats_body() and the rest all resolve to the default body without consulting it. ZSTD_cpuSupportsBmi2() nevertheless issues CPUID, which on x86 is two serializing instructions, and throws the answer away.
ZSTD_initDCtx_internal() already wraps its assignment in #if DYNAMIC_BMI2 - it has to, because the dctx->bmi2 field is itself declared under that #if. The two compress-side callers have no such guard, and ZSTD_CCtx_s::bmi2 is unconditional, so they probe unconditionally.
Put the test inside ZSTD_cpuSupportsBmi2() so every caller gets it without having to remember.
--- lib/zstd/common/zstd_internal.h | 5 +++++ 1 file changed, 5 insertions(+)
lib/zstd/common/zstd_internal.h +5 -0
@@ -311,8 +311,13 @@ size_t ZSTD_decodeSeqHeaders(ZSTD_DCtx* dctx, int* nbSeqPtr,*/ MEM_STATIC int ZSTD_cpuSupportsBmi2(void) { +#if DYNAMIC_BMI2 ZSTD_cpuid_t cpuid =ZSTD_cpuid ();return ZSTD_cpuid_bmi1 (cpuid) &&ZSTD_cpuid_bmi2 (cpuid); +#else +/* Nothing looks at the flag in this configuration. */ +return 0 ; +#endif }#endif /* ZSTD_CCOMMON_H_MODULE */
Signature · 1 line
2.53.0-Meta
PATCH 3/3 zstd: probe the CPU for BMI2 support only once
In reply to Usama ArifZSTD_cpuSupportsBmi2() issues CPUID on every context setup for an answer that cannot change while the kernel is running. On x86 that is two serializing CPUID instructions, and the callers are not rare:
squashfs, erofs, btrfs, f2fs and crypto/zstd all initialise a context per operation, so a busy squashfs or zswap workload pays for it per block or per page. Under KVM it is worse, because CPUID is an unconditional VM exit.
Cache the result. Keeping the cache as a single int with a negative sentinel, rather than a copy of ZSTD_cpuid_t, keeps it to one word: a racing pair of probes computes the same value from the same CPUID leaf, so the unsynchronized access is benign, and READ_ONCE()/WRITE_ONCE() keep the compiler and KCSAN in agreement about that.
ZSTD_cpuSupportsBmi2() is MEM_STATIC, so each translation unit that inlines it gets its own cache - three in a modular build, plus one in each preboot decompressor. That is a handful of ints in bss and one extra probe apiece, not worth avoiding.
The cached answer is the one the probing CPU reported. zstd could already be migrated between the probe and the use of the flag, so this does not introduce a heterogeneity question that was not there before.
--- lib/zstd/common/zstd_internal.h | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-)
lib/zstd/common/zstd_internal.h +15 -2
@@ -312,8 +312,21 @@ size_t ZSTD_decodeSeqHeaders(ZSTD_DCtx* dctx, int* nbSeqPtr, MEM_STATIC int ZSTD_cpuSupportsBmi2(void) {#if DYNAMIC_BMI2 -ZSTD_cpuid_t cpuid =ZSTD_cpuid (); -return ZSTD_cpuid_bmi1 (cpuid) &&ZSTD_cpuid_bmi2 (cpuid); +/* +* The answer cannot change over the life of the kernel, so probe +* once. Racing probes compute the same value, so the unsynchronized +* access is benign; the annotations are there to keep it that way. +*/ +static int supported =-1 ; +int s =READ_ONCE (supported); + +if (s <0 ) { +ZSTD_cpuid_t const cpuid =ZSTD_cpuid (); + + s =ZSTD_cpuid_bmi1 (cpuid) &&ZSTD_cpuid_bmi2 (cpuid); +WRITE_ONCE (supported, s); + } +return s;#else /* Nothing looks at the flag in this configuration. */ return 0 ;
Signature · 1 line
2.53.0-Meta
Quoted 22 lines · Usama Arif
zstd picks between BMI2 and generic code paths at runtime, and issues CPUID to decide every time a compression or decompression context is set up. The answer cannot change while the kernel is running.
It is not a cold path: squashfs calls
zstd_init_dstream()for every block it decompresses, and erofs, btrfs, f2fs andcrypto/zstdall initialise a context per operation. Each probe is two serializing CPUID instructions on x86.Patch 1 routes
ZSTD_initStaticCCtx()throughZSTD_cpuSupportsBmi2()instead of open-coding the probe, which also fixes it testing for BMI2 without BMI1 - the bodies it selects are taggedTARGET_ATTRIBUTE("lzcnt,bmi,bmi2"), so both are needed. No CPU in the field implements BMI2 without BMI1, so this is latent. Patch 2 skips the probe whenDYNAMIC_BMI2is 0, where every consumer ignores the flag anyway. Patch 3 caches the result.A 4 KiB
crypto_acompbenchmark [1] in a one-vCPU KVM guest, twelve boots of nine 30,000-operation rounds, median per-round mean over 108 rounds:compress decompress
Quoted 8 lines
unpatched 16,756 ns 3,455 ns patched 13,646 ns 1,002 ns -3,110 ns -2,452 ns (18.6%) (71.0%)The main reason is because CPUID is an unconditional VM exit.
[1] https://gist.github.com/uarif1/5cf02f0e22c23f0d1b3d84348f12914c
Awesome! I'm no zstd expert, but this looks very nice. Thanks for fixing it. I'll defer mostly to Nick (is the fb.com email still working?) and Herbert for correctness checking.
BTW, I think this has been reported in the past:
https://lore.kernel.org/all/CAJxJ_jhvyMukPLThpgcdCMHwbp3b3bFvc4Va1cK79_3z6ubhwQ@mail.gmail.com/
Quoted 30 lines · Usama Arif
zstd picks between BMI2 and generic code paths at runtime, and issues CPUID to decide every time a compression or decompression context is set up. The answer cannot change while the kernel is running.
It is not a cold path: squashfs calls
zstd_init_dstream()for every block it decompresses, and erofs, btrfs, f2fs andcrypto/zstdall initialise a context per operation. Each probe is two serializing CPUID instructions on x86.Patch 1 routes
ZSTD_initStaticCCtx()throughZSTD_cpuSupportsBmi2()instead of open-coding the probe, which also fixes it testing for BMI2 without BMI1 - the bodies it selects are taggedTARGET_ATTRIBUTE("lzcnt,bmi,bmi2"), so both are needed. No CPU in the field implements BMI2 without BMI1, so this is latent. Patch 2 skips the probe whenDYNAMIC_BMI2is 0, where every consumer ignores the flag anyway. Patch 3 caches the result.A 4 KiB
crypto_acompbenchmark [1] in a one-vCPU KVM guest, twelve boots of nine 30,000-operation rounds, median per-round mean over 108 rounds:compress decompress
unpatched 16,756 ns 3,455 ns patched 13,646 ns 1,002 ns -3,110 ns -2,452 ns (18.6%) (71.0%)The main reason is because CPUID is an unconditional VM exit.
[1] https://gist.github.com/uarif1/5cf02f0e22c23f0d1b3d84348f12914c
Quoted 8 lines
Usama Arif (3):
zstd: useZSTD_cpuSupportsBmi2()inZSTD_initStaticCCtx()
zstd: skip the BMI2 probe when dynamic BMI2 dispatch is disabled
zstd: probe the CPU for BMI2 support only oncelib/zstd/common/zstd_internal.h | 22 ++++++++++++++++++++-- lib/zstd/compress/zstd_compress.c | 2 +- 2 files changed, 21 insertions(+), 3 deletions(-)
Why not just use cpu_feature_enabled(X86_FEATURE_BMI2), which compiles down to a static branch? All these issues are caused by lib/zstd/ using its own custom CPU feature detection code, instead of the normal CPU feature detection code that the rest of the kernel uses.
- Eric
Quoted 40 lines · Eric Biggers
Quoted 30 lines · Usama Arif
zstd picks between BMI2 and generic code paths at runtime, and issues CPUID to decide every time a compression or decompression context is set up. The answer cannot change while the kernel is running.
It is not a cold path: squashfs calls
zstd_init_dstream()for every block it decompresses, and erofs, btrfs, f2fs andcrypto/zstdall initialise a context per operation. Each probe is two serializing CPUID instructions on x86.Patch 1 routes
ZSTD_initStaticCCtx()throughZSTD_cpuSupportsBmi2()instead of open-coding the probe, which also fixes it testing for BMI2 without BMI1 - the bodies it selects are taggedTARGET_ATTRIBUTE("lzcnt,bmi,bmi2"), so both are needed. No CPU in the field implements BMI2 without BMI1, so this is latent. Patch 2 skips the probe whenDYNAMIC_BMI2is 0, where every consumer ignores the flag anyway. Patch 3 caches the result.A 4 KiB
crypto_acompbenchmark [1] in a one-vCPU KVM guest, twelve boots of nine 30,000-operation rounds, median per-round mean over 108 rounds:compress decompress
unpatched 16,756 ns 3,455 ns patched 13,646 ns 1,002 ns -3,110 ns -2,452 ns (18.6%) (71.0%)The main reason is because CPUID is an unconditional VM exit.
[1] https://gist.github.com/uarif1/5cf02f0e22c23f0d1b3d84348f12914c
Quoted 8 lines
Usama Arif (3):
zstd: useZSTD_cpuSupportsBmi2()inZSTD_initStaticCCtx()
zstd: skip the BMI2 probe when dynamic BMI2 dispatch is disabled
zstd: probe the CPU for BMI2 support only oncelib/zstd/common/zstd_internal.h | 22 ++++++++++++++++++++-- lib/zstd/compress/zstd_compress.c | 2 +- 2 files changed, 21 insertions(+), 3 deletions(-)
Quoted 6 lines
Why not just use
cpu_feature_enabled(X86_FEATURE_BMI2), which compiles down to a static branch? All these issues are caused bylib/zstd/using its own custom CPU feature detection code, instead of the normal CPU feature detection code that the rest of the kernel uses.- Eric
The only issue I saw with that was that zstd is a standalone library that is imported, so I am not sure how using cpu_feature_enabled() would work for the maintainers. If the maintainers are happy with it, I think the below patch is much better.
From 0b21d945f579cbb5e41b92b4c9306e9d5bac84f1 Mon Sep 17 00:00:00 2001
From: Usama Arif <[email protected]>
Date: Thu, 27 Aug 2026 05:34:41 -0700
Subject: [PATCH] zstd: use kernel CPU feature detection on x86
Zstd currently probes CPUID while initializing each compression or decompression context. This bypasses the x86 feature policy used by the rest of the kernel and repeats a serializing instruction sequence for every context.
Use cpu_feature_enabled() in the normal x86 compressor and decompressor objects. Check ABM, BMI1, and BMI2 because the dispatched functions are compiled with lzcnt, bmi, and bmi2. The checks are alternatives-patched at boot.
The effect is especially visible under virtualization, where CPUID normally causes a VM exit. A 4 KiB crypto_acomp benchmark was run in one-vCPU KVM guests. Comparing the unpatched baseline with this three-patch series, the median reported ns/op values were:
before after
compression 16,777 13,635 ns/op (-18.7%)
decompression 3,454 1,006 ns/op (-70.9%)
Keep the existing raw CPUID fallback for preboot and other builds which cannot use the normal x86 feature infrastructure. Also retain the early return when dynamic dispatch is disabled.
--- lib/zstd/Makefile | 5 +++++ lib/zstd/common/zstd_internal.h | 18 ++++++++++++++---- 2 files changed, 19 insertions(+), 4 deletions(-)
lib/zstd/Makefile +5 -0
@@ -42,3 +42,8 @@ zstd_common-y := \ common/error_private.o \ common/fse_decompress.o \ common/zstd_common.o \ + +ifeq ($(CONFIG_X86),y) +CFLAGS_compress/zstd_compress.o += -DZSTD_USE_KERNEL_CPU_FEATURES +CFLAGS_decompress/zstd_decompress.o += -DZSTD_USE_KERNEL_CPU_FEATURES +endif
lib/zstd/common/zstd_internal.h +14 -4
@@ -31,6 +31,11 @@#include "fse.h" #include "huf.h" #include <linux/xxhash.h> /* XXH_reset, update, digest */ + +/* Use the kernel's CPU feature policy in normal x86 kernel builds. */ +#if defined(ZSTD_USE_KERNEL_CPU_FEATURES ) +#include <asm/cpufeature.h> +#endif #define ZSTD_TRACE 0/* ---- static assert (debug) --- */
@@ -311,12 +316,17 @@ size_t ZSTD_decodeSeqHeaders(ZSTD_DCtx* dctx, int* nbSeqPtr,*/ MEM_STATIC int ZSTD_cpuSupportsBmi2(void) { -#if DYNAMIC_BMI2 -ZSTD_cpuid_t cpuid =ZSTD_cpuid (); -return ZSTD_cpuid_bmi1 (cpuid) &&ZSTD_cpuid_bmi2 (cpuid); -#else +#if !DYNAMIC_BMI2 /* Nothing looks at the flag in this configuration. */ return 0 ; +#elif defined(ZSTD_USE_KERNEL_CPU_FEATURES ) +return cpu_feature_enabled (X86_FEATURE_ABM ) && +cpu_feature_enabled (X86_FEATURE_BMI1 ) && +cpu_feature_enabled (X86_FEATURE_BMI2 ); +#else +ZSTD_cpuid_t cpuid =ZSTD_cpuid (); +return ZSTD_cpuid_bmi1 (cpuid) && +ZSTD_cpuid_bmi2 (cpuid);#endif }
Signature · 1 line
2.53.0-Meta