summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2024-11-28 04:34:11 +0300
committerSean Christopherson <seanjc@google.com>2024-12-19 01:20:09 +0300
commite592ec657d84acba6562b3bfbd699769dc54e294 (patch)
tree3aea60f2943b1050b6b93d5afa170a7d07ab034d /tools/perf/scripts/python/exported-sql-viewer.py
parentd4b9ff3d55dede868f43c4541ba999c109dbadcb (diff)
downloadlinux-e592ec657d84acba6562b3bfbd699769dc54e294.tar.xz
KVM: x86: Initialize guest cpu_caps based on KVM support
Constrain all guest cpu_caps based on KVM support instead of constraining only the few features that KVM _currently_ needs to verify are actually supported by KVM. The intent of cpu_caps is to track what the guest is actually capable of using, not the raw, unfiltered CPUID values that the guest sees. I.e. KVM should always consult it's only support when making decisions based on guest CPUID, and the only reason KVM has historically made the checks opt-in was due to lack of centralized tracking. Suggested-by: Maxim Levitsky <mlevitsk@redhat.com> Link: https://lore.kernel.org/r/20241128013424.4096668-45-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