linux-toradex.git/kernel/scftorture.c, branch v6.11-rc5

scftorture: Make torture_type static

2024-05-30T22:31:51+00:00

Fix the 'make C=1' warning:
kernel/scftorture.c:71:6: warning: symbol 'torture_type' was not declared. Should it be static?

Signed-off-by: Jeff Johnson 
Signed-off-by: Paul E. McKenney

scftorture: Add MODULE_DESCRIPTION()

2024-05-30T22:31:45+00:00

Fix the 'make W=1' warning:
WARNING: modpost: missing MODULE_DESCRIPTION() in kernel/scftorture.o

Signed-off-by: Jeff Johnson 
Signed-off-by: Paul E. McKenney

scftorture: Pause testing after memory-allocation failure

2023-07-14T22:02:57+00:00

The scftorture test can quickly execute a large number of calls to no-wait
smp_call_function(), each of which holds a block of memory until the
corresponding handler is invoked.  Especially when the longwait module
parameter is specified, this can chew up an arbitrarily large amount
of memory.  This commit therefore blocks after each memory-allocation
failure, with the duration a function of longwait.

Signed-off-by: Paul E. McKenney

scftorture: Forgive memory-allocation failure if KASAN

2023-07-14T22:02:57+00:00

Kernels built with CONFIG_KASAN=y quarantine newly freed memory in order
to better detect use-after-free errors.  However, this can exhaust memory
more quickly in allocator-heavy tests, which can result in spurious
scftorture failure.  This commit therefore forgives memory-allocation
failure in kernels built with CONFIG_KASAN=y, but continues counting
the errors for use in detailed test-result analyses.

Signed-off-by: Paul E. McKenney

scftorture: Fix distribution of short handler delays

2022-04-12T00:07:29+00:00

The scftorture test module's scf_handler() function is supposed to provide
three different distributions of short delays (including "no delay") and
one distribution of long delays, if specified by the scftorture.longwait
module parameter.  However, the second of the two non-zero-wait short delays
is disabled due to the first such delay's "goto out" not being enclosed in
the "then" clause with the "udelay()".

This commit therefore adjusts the code to provide the intended set of
delays.

Fixes: e9d338a0b179 ("scftorture: Add smp_call_function() torture test")
Signed-off-by: Paul E. McKenney

scftorture: Always log error message

2021-12-08T00:36:17+00:00

Unconditionally log messages corresponding to errors.

Acked-by: Davidlohr Bueso 
Signed-off-by: Li Zhijian 
Signed-off-by: Paul E. McKenney

scftorture: Remove unused SCFTORTOUT

2021-12-08T00:36:17+00:00

There are no longer any users of SCFTORTOUT(), so this commit removes it.

Acked-by: Davidlohr Bueso 
Signed-off-by: Li Zhijian 
Signed-off-by: Paul E. McKenney

scftorture: Add missing '\n' to flush message

2021-12-08T00:36:17+00:00

Add '\n' to macros to flush message for each call.

Acked-by: Davidlohr Bueso 
Signed-off-by: Li Zhijian 
Signed-off-by: Paul E. McKenney

scftorture: Warn on individual scf_torture_init() error conditions

2021-09-16T17:27:48+00:00

When running scftorture as a module, any scf_torture_init() issues will be
reflected in the error code from modprobe or insmod, as the case may be.
However, these error codes are not available when running scftorture
built-in, for example, when using the kvm.sh script.  This commit
therefore adds WARN_ON_ONCE() to allow distinguishing scf_torture_init()
errors when running scftorture built-in.

Signed-off-by: Paul E. McKenney

scftorture: Count reschedule IPIs

2021-09-16T17:27:48+00:00

Currently, only those IPIs that invoke scftorture's scf_handler()
IPI handler function are counted.  This means that runs exercising
only scftorture.weight_resched will look like they have made no forward
progress, resulting in "GP HANG" complaints from the rcutorture scripting.
This commit therefore increments the scf_invoked_count per-CPU counter
immediately after calling resched_cpu().

Fixes: 1ac78b49d61d4 ("scftorture: Add an alternative IPI vector")
Signed-off-by: Paul E. McKenney