On Fri, Jul 15, 2022 at 7:48 AM Daniel Latypov dlatypov@google.com wrote:
On Thu, Jul 14, 2022 at 4:45 PM Daniel Latypov dlatypov@google.com wrote:
Ack. So concretely, so then a final result like this?
$ cat kernel/kcsan/.kunitconfig # Note that the KCSAN tests need to run on an SMP setup. # Under kunit_tool, this can be done by using the x86_64-smp # qemu-based architecture:
Oops, this bit would need to be updated to something like:
# Under kunit_tool, this can be done by using --qemu_args:
# ./tools/testing/kunit/kunit.py run --kunitconfig=kernel/kcsan --arch=x86_64 --qemu_args='-smp 8'
CONFIG_KUNIT=y
CONFIG_DEBUG_KERNEL=y
CONFIG_KCSAN=y CONFIG_KCSAN_KUNIT_TEST=y
# Need some level of concurrency to test a concurrency sanitizer. CONFIG_SMP=y
# This prevents the test from timing out on many setups. Feel free to remove # (or alter) this, in conjunction with setting a different test timeout with, # for example, the --timeout kunit_tool option. CONFIG_KCSAN_REPORT_ONCE_IN_MS=100
Thanks everyone. I've sent out a v2 with just this patch here: https://lore.kernel.org/linux-kselftest/20220715064052.2673958-1-davidgow@go...
I expect we'll take it in via the KUnit branch, as it's most useful with the --qemu_args option.
Cheers, -- David