On Mon, Feb 10, 2025 at 12:46 PM David Hildenbrand <david@xxxxxxxxxx> wrote: > > On 10.02.25 20:35, John Hubbard wrote: > > On 2/9/25 11:54 PM, Geert Uytterhoeven wrote: > >> On Sat, 8 Feb 2025 at 18:53, Yury Norov <yury.norov@xxxxxxxxx> wrote: > >>> On Fri, Feb 07, 2025 at 03:14:01PM -0500, Tamir Duberstein wrote: > >>>> On 7/27/24 12:35 AM, Shuah Khan wrote: > > ... > >>>> The crux of the argument seems to be that the config help text is taken > >>>> to describe the author's intent with the fragment "at boot". I think > >> > >> IMO, "at boot" is a misnomer, as most tests can be either builtin > >> or modular. > > > > Right. > > > >> > >>> KUNIT is disabled in defconfig, at least on x86_64. It is also disabled > >>> on my Ubuntu 24.04 machine. If I take your patches, I'll be unable to > > > > OK so I just bought a shiny new test machine, and installed one of the > > big name distros on it, hoping they've moved ahead and bought into the kunit > > story... > > > > $ grep KUNIT /boot/config-6.8.0-52-generic > > # CONFIG_KUNIT is not set > > > > ...gagghh! No such luck. One more data point, in support of Yuri's complaint. :) > > > >> > >> I think distros should start setting CONFIG_KUNIT=m. > > > > Yes they should! kunit really does have important advantages for many use > > cases, including bitmaps here, and "CONFIG_KUNIT is not set" is the main > > obstacle. > > > Let me add a few people to Cc who might be able to influence some > distros. > > > > thanks, > > > Fedora has it. > > CS-10 has it (-> RHEL-10): > redhat/configs/common/generic/CONFIG_KUNIT:CONFIG_KUNIT=m > > https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-10/-/blob/main/redhat/configs/common/generic/CONFIG_KUNIT?ref_type=heads > > CS-9 has it (-> RHEL-9): > redhat/configs/common/generic/CONFIG_KUNIT:CONFIG_KUNIT=m > > https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/blob/main/redhat/configs/common/generic/CONFIG_KUNIT?ref_type=heads > > So I think from the RH side everything is properly set? > > Let me CC Nico, he did some KUNIT work in the past. Yeah that is correct! I enabled KUNIT in our environments a few years ago. We enable it as a module and use our own wrapper to exercise the code. For RHEL and Centos these kunit modules are only shipped internally for testing; However fedora-rawhide makes these modules available in the kernel-modules-internal package. To test this you can follow this to install rawhide-vm: https://developer.fedoraproject.org/tools/virt-builder/about.html then inside the vm: yum install kernel-modules-internal add the kunit.enable=1 to the cmdline reboot vm modprobe kunit modprobe <test_name> Hopefully that helps! -- Nico > > > -- > Cheers, > > David / dhildenb >
