Ktest comes with numerous, battle-hardened configuration options allowing you to control, for example, compile options, kernel configuration, bootloader type, kernel install method, iterations, timeout lengths, power cycle command, and test success criteria. (Those bots are nice for less common configs though.) Code reviewers' moods improve too because each patch will stand alone with all the necessary code. For your chosen configs, the series will be cleanly bisectable and won't trigger upstream build bots with easily avoided errors and warnings mid-series. Where ktest is especially useful, though, is in its ability to do these things for each patch in a series, thereby freeing you from a significant amount of tedium. It can test multiple kernel configurations, in case the code you're touching is sensitive to that, and multiple architectures, in case you want to automate cross-compilation. See /home/penguin/src/ktest/log.ktest for more info. Warning: symbol 'totalcma_pages' was not declared. home/penguin/kernel/worktrees/ktest-blog/mm/page_alloc.c:135:15: For instance, here's ktest flagging a new warning during a build:ĬRITICAL FAILURE. The script can detect build failures, newly introduced warnings, runtime hangs and splats, and script failures. It's up to you how far in the process ktest will go, so it's possible to build, or build and boot, or do all three steps. Ktest can build a kernel on a host system, boot it on a target machine, and run a script on the target. This post will cover ktest's capabilities and requirements, and give concrete examples of how to use it in one specific environment, a single physical machine with a qemu VM run under virsh. The script is aimed at individual kernel programmers testing their patch series, and provides an alternative to the Autotest framework, which is powerful but quite involved for one person to set up. In October 2010, Steven Rostedt announced on the LKML that he was working on a script called to automate certain aspects of Linux kernel testing. You will learn the principles as well as actual practice.Ktest: Automated Testing For Kernel Programmers
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |