On 2/10/25 3:10 PM, Nico Pache wrote:
...
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
Great news, thanks for the quick answers for Red Hat. "Already done" is as
good as it gets, for this kind of question. :)
thanks,
--
John Hubbard
