On Thu, Feb 13, 2025 at 6:59 AM Peter Zijlstra <pet...@infradead.org> wrote: > > On Thu, Feb 13, 2025 at 06:40:20AM -0500, Tamir Duberstein wrote: > > Convert this unit test to a KUnit test. This allows the test to benefit > > from the KUnit tooling. Note that care is taken to avoid test-ending > > assertions in worker threads, which is unsafe in KUnit (and wasn't done > > before this change either). > > So this was something simple, and now I need to know how to operate this > kunit nonsense :-( > > How is that an improvement?
Hi Peter, David enumerated some of the benefits of KUnit in another thread: https://lore.kernel.org/all/CABVgOS=kzrm2dwyp1hzvs0zh7vqulxmty2t2ti53dqadrw+...@mail.gmail.com/. My personal reason for preferring KUnit is that it's much easier to run from userspace; the tooling takes care of building, starting the VM, running the tests, and producing a human-friendly report. Anecdotally I've seen evidence that e.g. Intel's 0-day runs all KUnit tests but not all kselftests (e.g. https://lore.kernel.org/all/202502090223.qcymbjwt-...@intel.com/). Tamir
