diff options
| author | Sean Christopherson <seanjc@google.com> | 2022-11-25 20:58:38 +0800 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-11-28 13:33:25 -0500 |
| commit | c4690d016182d271a862767145db8b2bc792f4a8 (patch) | |
| tree | fcd1642b971fb2eda321154a67ee7a81e6131138 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 7927e27549d3f02354233a9ab3f28e0080ede29b (diff) | |
| download | linux-c4690d016182d271a862767145db8b2bc792f4a8.tar.gz linux-c4690d016182d271a862767145db8b2bc792f4a8.tar.bz2 linux-c4690d016182d271a862767145db8b2bc792f4a8.zip | |
KVM: x86: Add BUILD_BUG_ON() to detect bad usage of "scattered" flags
Add a compile-time assert in the SF() macro to detect improper usage,
i.e. to detect passing in an X86_FEATURE_* flag that isn't actually
scattered by the kernel. Upcoming feature flags will be 100% KVM-only
and will have X86_FEATURE_* macros that point at a kvm_only_cpuid_leafs
word, not a kernel-defined word. Using SF() and thus boot_cpu_has() for
such feature flags would access memory beyond x86_capability[NCAPINTS]
and at best incorrectly hide a feature, and at worst leak kernel state to
userspace.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20221125125845.1182922-2-jiaxi.chen@linux.intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions