Lines Matching full:changes

54 Changes that target the next release are routed through the KVM x86 tree.  Pull
100 and/or has more than superficial changes to other architectures' code.  Multi-
163 changes, i.e. for arch/x86/kernel/kvm.c.  Do not use file names or complete file
198 a short blurb on the actual changes, and then follow up with the context and
251 obvious, the tests need to pass).  The only exception is for changes that have
256 For changes that touch KVM's shadow paging code, running with TDP (EPT/NPT)
257 disabled is mandatory.  For changes that affect common KVM MMU code, running
258 with TDP disabled is strongly encouraged.  For all other changes, if the code
263 a failure is not due to your changes, verify that the *exact same* failure
264 occurs with and without your changes.
266 Changes that touch reStructured Text documentation, i.e. .rst files, must build
321 wasn't Cc'd on the bug report or if the list of recipients changes between
348 KVM selftests that are associated with KVM changes, e.g. regression tests for
349 bug fixes, should be posted along with the KVM changes as a single series.  The
350 standard kernel rules for bisection apply, i.e. KVM changes that result in test
357 KVM patches, first post the KVM changes and then provide a lore Link: to the
381 patch's SHA1 changes.  However, in some scenarios, e.g. if all KVM x86 branches