Lines Matching full:to

1 # Welcome to kvm-unit-tests
11 To create the test images do:
30 clang may be used as an alternative to gcc.
44 The tests can be built as standalone.  To create and use standalone tests do:
49     (go to somewhere)
58 Then use the runner script to detect the correct invocation and
66 to run them all.
72 To select a specific QEMU binary though, specify the QEMU=path/to/binary
77 To select an accelerator, for example "kvm", "hvf" or "tcg", specify the
82 For running tests that involve migration from one QEMU instance to another
83 you also need to have the "ncat" binary (from the nmap.org project) installed,
93 To select a kvmtool binary, specify the KVMTOOL=path/to/binary environment
105 example, extra QEMU parameters and time to execute limited, the
110 to.  So that a given group can be executed by specifying its name in the
123 may be passed with '-initrd file' to become the unit test's environ,
139 Some tests are not safe to run by default, as they may crash the
140 host. kvm-unit-tests provides two ways to handle tests like those.
142  1) Adding 'nodefault' to the groups field for the unit test in the
169         to 'y'.)
172 conditionals to their respective minimum kernel versions.  By default,
174 from the ./errata.txt file and the host's kernel version is provided to
192 Currently there is a mix of indentation styles so any changes to
202   - While the kernel standard requires 80 columns, we allow up to 120.
206 Please try to adhere to the following patterns when adding
219 You can add the following to .git/config to do this automatically for you:
224 Additionally it's helpful to have a common order of file types in patches.
225 Our chosen order attempts to place the more declarative files before
227 code. git-diff's orderFile feature allows us to specify the order in a
231 We strive to follow the Linux kernels coding style so it's recommended
232 to run the kernel's ./scripts/checkpatch.pl on new patches.