From: kernel test robot <lkp@intel.com>
To: Martin Willi <martin@strongswan.org>, Eric Biggers <ebiggers@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Ard Biesheuvel <ardb@kernel.org>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH] lib/crypto: x86/chacha: Add a 16-block AVX-512 variant
Date: Thu, 6 Aug 2026 15:40:34 +0800 [thread overview]
Message-ID: <202608061529.D3FMYdiE-lkp@intel.com> (raw)
In-Reply-To: <20260722153247.630519-1-martin@strongswan.org>
Hi Martin,
kernel test robot noticed the following build errors:
[auto build test ERROR on linux-review/Eric-Biggers/x86-fpu-Check-for-missing-AVX-and-AVX-512-xstate-bits/20260626-124221]
url: https://github.com/intel-lab-lkp/linux/commits/Martin-Willi/lib-crypto-x86-chacha-Add-a-16-block-AVX-512-variant/20260805-221950
base: https://github.com/intel-lab-lkp/linux Eric-Biggers/x86-fpu-Check-for-missing-AVX-and-AVX-512-xstate-bits/20260626-124221
patch link: https://lore.kernel.org/r/20260722153247.630519-1-martin%40strongswan.org
patch subject: [PATCH] lib/crypto: x86/chacha: Add a 16-block AVX-512 variant
config: x86_64-randconfig-075-20260806 (https://download.01.org/0day-ci/archive/20260806/202608061529.D3FMYdiE-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260806/202608061529.D3FMYdiE-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608061529.D3FMYdiE-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from lib/crypto/chacha.c:35:
>> lib/crypto/x86/chacha.h:199:8: error: call to undeclared function 'cpu_has_xfeatures'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
199 | cpu_has_xfeatures(XFEATURE_MASK_AVX512, NULL))
| ^
1 error generated.
vim +/cpu_has_xfeatures +199 lib/crypto/x86/chacha.h
180
181 #define chacha_mod_init_arch chacha_mod_init_arch
182 static void chacha_mod_init_arch(void)
183 {
184 if (!boot_cpu_has(X86_FEATURE_SSSE3))
185 return;
186
187 static_branch_enable(&chacha_use_simd);
188
189 if (boot_cpu_has(X86_FEATURE_AVX) &&
190 boot_cpu_has(X86_FEATURE_AVX2)) {
191 static_branch_enable(&chacha_use_avx2);
192
193 if (boot_cpu_has(X86_FEATURE_AVX512VL) &&
194 boot_cpu_has(X86_FEATURE_AVX512BW)) { /* kmovq */
195 static_branch_enable(&chacha_use_avx512vl);
196
197 if (boot_cpu_has(X86_FEATURE_AVX512F) &&
198 !boot_cpu_has(X86_FEATURE_PREFER_YMM) &&
> 199 cpu_has_xfeatures(XFEATURE_MASK_AVX512, NULL))
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-08-06 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 15:32 [PATCH] lib/crypto: x86/chacha: Add a 16-block AVX-512 variant Martin Willi
2026-07-22 23:24 ` Eric Biggers
2026-07-23 11:03 ` Martin Willi
2026-08-06 1:16 ` kernel test robot
2026-08-06 6:07 ` kernel test robot
2026-08-06 7:40 ` kernel test robot [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=202608061529.D3FMYdiE-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin@strongswan.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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