[RFC PATCH v1 1/1] perf test: Increase load in lock contention test on low-activity systems

[Jan Polensky <japo@linux.ibm.com>]

On low-activity systems, the 'kernel lock contention analysis test'
often fails due to insufficient system load. To address this, the test
now increases load by using multiple groups and threads in 'perf bench
sched messaging', scaled to the number of available CPUs.

Signed-off-by: Jan Polensky <japo@linux.ibm.com>
---
 tools/perf/tests/shell/lock_contention.sh | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/tools/perf/tests/shell/lock_contention.sh b/tools/perf/tests/shell/lock_contention.sh
index 30d195d4c62f..e859e1503b5c 100755
--- a/tools/perf/tests/shell/lock_contention.sh
+++ b/tools/perf/tests/shell/lock_contention.sh
@@ -44,7 +44,8 @@ check() {
 test_record()
 {
 	echo "Testing perf lock record and perf lock contention"
-	perf lock record -o ${perfdata} -- perf bench sched messaging > /dev/null 2>&1
+	perf lock record -o ${perfdata} -- perf bench sched messaging \
+		--group "$(nproc)" --thread "$(nproc)" > /dev/null 2>&1
 	# the output goes to the stderr and we expect only 1 output (-E 1)
 	perf lock contention -i ${perfdata} -E 1 -q 2> ${result}
 	if [ "$(cat "${result}" | wc -l)" != "1" ]; then
--
2.48.1