On October 4, 2024 7:33:38 AM GMT+02:00, Manali Shukla
wrote:
>Misbehaving guests can cause bus locks to degrade the performance of
>the system. The Bus Lock Threshold feature can be used to address this
>issue by providing capability to the hypervisor to limit guest's
>ability to generate bus lo
Rather than using symlinks to find the vgetrandom-chacha.S file for each
arch, store this in a file that uses the compiler to determine
architecture, and then make use of weak symbols to skip the test on
architectures that don't provide the code.
Signed-off-by: Jason A. Donenfeld
---
tools/arch/
The chacha test can build anywhere that the vgetrandom-chacha.S file is
available, so condition it on the existence of that file, rather than a
specific arch.
There is one wrinkle, which is that x86 and x86_64 are the same ARCH,
but the code is only functional for x86_64. So filter out the test fo
Improve the error and skip condition messages to let the developer know
precisely where a test has failed. Also make better use of the ksft api
for this.
Signed-off-by: Jason A. Donenfeld
---
.../testing/selftests/vDSO/vdso_test_chacha.c | 27 ---
.../selftests/vDSO/vdso_test_getrandom.c
Rather than building on supported archs, build on all archs, and then
use the presence of the symbol in the vDSO to either skip the test or
move forward with it.
Note that this means that this test no longer checks whether the symbol
was correctly added to the kernel. But hopefully this will be cl
I'll send a v2.
it date: 2 days ago
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project
3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build):
(https://download.01.org/0day-ci/archive/20241005/202410051432.uazav7yv-...@intel.com/reproduce)
If you fix the issue in a separate pa
Hi Manali,
kernel test robot noticed the following build warnings:
[auto build test WARNING on efbc6bd090f48ccf64f7a8dd5daea775821d57ec]
url:
https://github.com/intel-lab-lkp/linux/commits/Manali-Shukla/x86-cpufeatures-Add-CPUID-feature-bit-for-the-Bus-Lock-Threshold/20241004-133639
base:
This patch is a follow-up task from a discussion stemming from point 3
in a recent patch introducing the int_pow kunit test [1] and
documentation regarding kunit test style and nomenclature [2].
Colocate all kunit test suites in lib/math/tests/ and
follow recommended naming convention for files _k
