This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
start [2015/10/21 15:36] Luis R. Rodriguez created page |
start [2015/10/21 16:25] Tyler Baker |
||
---|---|---|---|
Line 5: | Line 5: | ||
===== kselftest ===== | ===== kselftest ===== | ||
- | These are the scripted tests in place upstream on the Linux kernel under the '''kselftest''' target of the top level Makefile. The tests are in place under tools/testing/selftests. This project has its own dedicated wiki: | + | These are the scripted tests in place upstream on the Linux kernel under the '''kselftest''' target of the top level Makefile. The tests are in place under tools/testing/selftests. This project has its own dedicated wiki [[https://kselftest.wiki.kernel.org/|kselftest]]. |
- | + | ||
- | * [[https://kselftest.wiki.kernel.org/|kselftest]] | + | |
===== coccicheck ===== | ===== coccicheck ===== | ||
- | These are the semantic tests in place in the kernel under the '''coccicheck''' target of the top level Makefile. These tests consists of a series of semantic patches written in Semantic Patch Language (SmPL) and make use of the [[http://coccinelle.lip6.fr/|Coccinelle engine]]. They can help you vet for correctness and avoid certain bugs which have been able to be expressed semantically. | + | These are the semantic tests in place in the kernel under the '''coccicheck''' target of the top level Makefile. For more details refer to the [[coccicheck]] page. |
- | + | ||
- | SmPL patches exist for these different types of categories: | + | |
- | + | ||
- | * api: help vet for correctness when using certain APIs | + | |
- | * free: avoid freeing bugs | + | |
- | * iterator: help vet for correctness when using kernel iterators | + | |
- | * locks: vet for correct locking behaviour and avoid bugs | + | |
- | * misc: things not covered in any of the other categories | + | |
- | * null: avoid null bugs | + | |
- | * tests: certain tests which are known to help with consistent kernel use | + | |
===== Zero Day Test ===== | ===== Zero Day Test ===== | ||
- | The Linux Zero Day tests are tests.. | + | The Linux Zero Day tests are tests. |
===== Marvin ===== | ===== Marvin ===== | ||
- | A series of performance-related test run against the Linux kernel. These tests are used by the SUSE performance team to continually test the Linux kernel for performance. See [[http://www.csn.ul.ie/~mel/blog/index.php?/archives/23-Continual-testing-of-mainline-kernels.html|Mel Gorman's blog announcing it]]. There are 4 components to '''Marvin''': | + | A series of performance-related test run against the Linux kernel. Refer to [[Marvin]] for more details. |
+ | |||
+ | ===== Xen tests ===== | ||
+ | |||
+ | These are the tests used to help test ongoing Xen development both on Linux and the Hypervisor when used on Linux. TBD. | ||
+ | |||
+ | ===== Undertaker ===== | ||
+ | |||
+ | Needs to be writtten. | ||
- | * [[https://github.com/gormanm/mmtests|MMTests]] | + | ===== kernelci.org ===== |
- | * Bob - builder that monitors git trees for new kernels to test, builds the kernel when it's released and schedules it to be tested | + | |
- | * Marvin - runs on the server and one instance exists per test machine. It checks the queue, prepares the test machine and executes tests when the machine is ready. | + | |
- | * Configuration Manager: responsible for reserving machines for exclusive use, managing power, managing serial consoles and deploying distributions automatically. | + | |
- | The inventory management does not have a specific name as it's different depending on where Marvin is setup. | + | A distributed farm of real and emulated hardware, focused on build, boot, and testing of upstream kernels. For more information, please visit the following links: [[http://kernelci.org|kernelci.org]] | [[http://wiki.kernelci.org|wiki]] | [[http://api.kernelci.org|api]] |