Lines Matching full:should

10 2.  Patches should be against kvm.git master or next branches.
18 5.  New features must default to off (userspace should explicitly request them).
19     Performance improvements can and should default to on.
21 6.  New cpu features should be exposed via KVM_GET_SUPPORTED_CPUID2,
24 7.  The feature should be testable (see below).
26 8.  Changes should be vendor neutral when possible.  Changes to common code
42 All features contributed to KVM, and in many cases bugfixes too, should be
70   The corresponding CPU features (if applicable) should be made available
77   These should be tested via ``kvm-unit-tests``; this more or less implies
91   While it's difficult to provide a single policy, you should ensure that
102   Selftests should test corner cases of the APIs, and should also cover
106   These should be supported by Linux guests, with limited exceptions for
109   as at least one of QEMU or crosvm, and guest firmware.  Selftests should