diff options
author | 2024-11-27 17:34:23 -0800 | |
---|---|---|
committer | 2024-12-18 14:20:22 -0800 | |
commit | ac9d1b7591a22e63f66a8c596390eccf821885e8 (patch) | |
tree | 4041b20e4b3799854a18e34d0d90bd5a9768daaa /scripts/generate_rust_analyzer.py | |
parent | KVM: x86: Explicitly track feature flags that require vendor enabling (diff) | |
download | wireguard-linux-ac9d1b7591a22e63f66a8c596390eccf821885e8.tar.xz wireguard-linux-ac9d1b7591a22e63f66a8c596390eccf821885e8.zip |
KVM: x86: Explicitly track feature flags that are enabled at runtime
Add one last (hopefully) CPUID feature macro, RUNTIME_F(), and use it
to track features that KVM supports, but that are only set at runtime
(in response to other state), and aren't advertised to userspace via
KVM_GET_SUPPORTED_CPUID.
Currently, RUNTIME_F() is mostly just documentation, but tracking all
KVM-supported features will allow for asserting, at build time, take),
that all features that are set, cleared, *or* checked by KVM are known to
kvm_set_cpu_caps().
No functional change intended.
Link: https://lore.kernel.org/r/20241128013424.4096668-57-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions