summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/interrupts.py
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2025-07-10 13:17:11 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2025-07-15 20:32:18 +0300
commit8a73c8dbb23010561c9bc78a7342c3ad0da11188 (patch)
treefd7a45becfc2a29d9619a235ca1db27e8100093c /scripts/gdb/linux/interrupts.py
parent83131d84694a85627f595b5ecd480f6ecb98b5aa (diff)
downloadlinux-8a73c8dbb23010561c9bc78a7342c3ad0da11188.tar.xz
KVM: Documentation: document how KVM is tested
Proper testing greatly simplifies both patch development and review, but it can be unclear what kind of userspace or guest support should accompany new features. Clarify maintainer expectations in terms of testing expectations; additionally, list the cases in which open-source userspace support is pretty much a necessity and its absence can only be mitigated by selftests. While these ideas have long been followed implicitly by KVM contributors and maintainers, formalize them in writing to provide consistent (though not universal) guidelines. Suggested-by: Rick Edgecombe <rick.p.edgecombe@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/gdb/linux/interrupts.py')
0 files changed, 0 insertions, 0 deletions