aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/lib/kdoc/kdoc_files.py
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2025-03-03 11:18:38 -0500
committerPaolo Bonzini <pbonzini@redhat.com>2025-03-14 14:20:58 -0400
commita4dae7c7a41d803a05192015b2d47aca8aca4abf (patch)
tree66921b7bc85f93329323df5bf2d8959fe27811f1 /scripts/lib/kdoc/kdoc_files.py
parentKVM: x86: do not allow re-enabling quirks (diff)
downloadlinux-rng-a4dae7c7a41d803a05192015b2d47aca8aca4abf.tar.xz
linux-rng-a4dae7c7a41d803a05192015b2d47aca8aca4abf.zip
KVM: x86: Allow vendor code to disable quirks
In some cases, the handling of quirks is split between platform-specific code and generic code, or it is done entirely in generic code, but the relevant bug does not trigger on some platforms; for example, this will be the case for "ignore guest PAT". Allow unaffected vendor modules to disable handling of a quirk for all VMs via a new entry in kvm_caps. Such quirks remain available in KVM_CAP_DISABLE_QUIRKS2, because that API tells userspace that KVM *knows* that some of its past behavior was bogus or just undesirable. In other words, it's plausible for userspace to refuse to run if a quirk is not listed by KVM_CAP_DISABLE_QUIRKS2, so preserve that and make it part of the API. As an example, mark KVM_X86_QUIRK_CD_NW_CLEARED as auto-disabled on Intel systems. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions