summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2024-08-02 23:04:20 +0300
committerSean Christopherson <seanjc@google.com>2024-11-01 19:22:28 +0300
commit0e3b70aa137cb29a407de38e5b660d939ab462a3 (patch)
treea69be465b0d7543a1c1d5262fb2d72fe6f593a7a /tools/perf/scripts/python/exported-sql-viewer.py
parent90a877216e6bd4cc336ecd85ad4e95cf7a1aa1c8 (diff)
downloadlinux-0e3b70aa137cb29a407de38e5b660d939ab462a3.tar.xz
KVM: x86: Document an erratum in KVM_SET_VCPU_EVENTS on Intel CPUs
Document a flaw in KVM's ABI which lets userspace attempt to inject a "bad" hardware exception event, and thus induce VM-Fail on Intel CPUs. Fixing the flaw is a fool's errand, as AMD doesn't sanity check the validity of the error code, Intel CPUs that support CET relax the check for Protected Mode, userspace can change the mode after queueing an exception, KVM ignores the error code when emulating Real Mode exceptions, and so on and so forth. The VM-Fail itself doesn't harm KVM or the kernel beyond triggering a ratelimited pr_warn(), so just document the oddity. Link: https://lore.kernel.org/r/20240802200420.330769-1-seanjc@google.com Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions