On Tue, Dec 12, 2023 at 12:35 AM Paul Heidekrüger <paul.heidekrueger@xxxxxx> wrote: > > Using CONFIG_FTRACE=y instead of CONFIG_TRACEPOINTS=y produces the same error > for me. > > So > > CONFIG_KUNIT=y > CONFIG_KUNIT_ALL_TESTS=n > CONFIG_FTRACE=y > CONFIG_KASAN=y > CONFIG_KASAN_GENERIC=y > CONFIG_KASAN_KUNIT_TEST=y > > produces > > ➜ ./tools/testing/kunit/kunit.py run --kunitconfig=mm/kasan/.kunitconfig --arch=arm64 > Configuring KUnit Kernel ... > Regenerating .config ... > Populating config with: > $ make ARCH=arm64 O=.kunit olddefconfig CC=clang > ERROR:root:Not all Kconfig options selected in kunitconfig were in the generated .config. > This is probably due to unsatisfied dependencies. > Missing: CONFIG_KASAN_KUNIT_TEST=y > > By that error message, CONFIG_FTRACE appears to be present in the generated > config, but CONFIG_KASAN_KUNIT_TEST still isn't. Presumably, > CONFIG_KASAN_KUNIT_TEST is missing because of an unsatisfied dependency, which > must be CONFIG_TRACEPOINTS, unless I'm missing something ... > > If I just generate an arm64 defconfig and select CONFIG_FTRACE=y, > CONFIG_TRACEPOINTS=y shows up in my .config. So, maybe this is kunit.py-related > then? > > Andrey, you said that the tests have been working for you; are you running them > with kunit.py? No, I just run the kernel built with a config file that I put together based on defconfig.
