From KVM

Contents 1 Contribute to KVM autotest 1.1 Get the source 1.2 Coding standards 1.3 Check your code 1.4 Send your patches

Contribute to KVM autotest

The KVM autotest project effort was merged back to the framework that originated the work, autotest. Autotest is a testing framework, developed in the most part using the python language.

Get the source

Please use the git tree, URL available here to clone the code and create patches.

Coding standards

Autotest has a peculiar coding standard system, that was agreed on and developed over the years by the project contributors. Make sure you check it out before writing code for the project. Of course, the actual code is an excellent practical source to understand how the coding standards work.

Check your code

Python, as any good dynamic language interpreted makes hard to spot little errors and inconsistencies that would've been easily found if the language was compiled. In order to mitigate this problem, you can use pylint, a program that can help you check for inconsistencies. Autotest ships with a utility script called utils/run_pylint.py here is the code, that will run pylint on a source file and spot all the errors and inconsistencies on it.

So we strongly suggest that you use run_pylint on all source files touched by your patch to see if you are not forgetting anything.

Send your patches

All patches must be sent to the autotest mailing list

Autotest mailing list autotest AT test kernel org

With a copy to the KVM mailing list

KVM mailing list kvm AT vger kernel org