On Fri, 2025-10-17 at 09:38 +0200, Nam Cao wrote:
Gabriele Monaco gmonaco@redhat.com writes:
Add a series of tests to validate the RV tracefs API and basic functionality.
Thanks for the writing this test. My bash knowledge is not great, and I'm not familiar with the existing ftrace test, so I am not able to review all the details. But looks good as far as I can tell:
Acked-by: Nam Cao namcao@linutronix.de
Thanks for the ack! I think that's good for now as it's going to go to Steve as a next step anyway.
I'm going to send a V2 with the following change just to increase the likelihood of a wwnr reaction and prepare a PR. I'll keep your ack there unless you explicitly mean otherwise.
Thanks, Gabriele
diff --git a/tools/testing/selftests/verification/test.d/rv_wwnr_printk.tc b/tools/testing/selftests/verification/test.d/rv_wwnr_printk.tc index bc0b2668bf7c..5a59432b1d93 100644 --- a/tools/testing/selftests/verification/test.d/rv_wwnr_printk.tc +++ b/tools/testing/selftests/verification/test.d/rv_wwnr_printk.tc @@ -4,9 +4,10 @@ # requires: available_reactors wwnr:monitor printk:reactor stress-ng:program
load() { # returns true if there was a reaction - local lines_before + local lines_before num + num=$((($(nproc) + 1) / 2)) lines_before=$(dmesg | wc -l) - stress-ng --cpu-sched 2 --timer 2 -t 5 -q + stress-ng --cpu-sched "$num" --timer "$num" -t 5 -q dmesg | tail -n $((lines_before + 1)) | grep -q "rv: monitor wwnr does not allow event" }