diff options
| author | Sean Christopherson <seanjc@google.com> | 2022-06-11 00:57:50 +0000 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-06-20 11:49:20 -0400 |
| commit | 0f4a7185270c4879fa40b33d7e07b6ac38353b34 (patch) | |
| tree | fde7d692cc3a7bb2496262439d417658bb5724c4 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | KVM: x86: Give host userspace full control of MSR_IA32_MISC_ENABLES (diff) | |
| download | linux-0f4a7185270c4879fa40b33d7e07b6ac38353b34.tar.gz linux-0f4a7185270c4879fa40b33d7e07b6ac38353b34.zip | |
KVM: VMX: Give host userspace full control of MSR_IA32_PERF_CAPABILITIES
Do not clear manipulate MSR_IA32_PERF_CAPABILITIES in intel_pmu_refresh(),
i.e. give userspace full control over capability/read-only MSRs. KVM is
not a babysitter, it is userspace's responsiblity to provide a valid and
coherent vCPU model.
Attempting to "help" the guest by forcing a consistent model creates edge
cases, and ironicially leads to inconsistent behavior.
Example #1: KVM doesn't do intel_pmu_refresh() when userspace writes
the MSR.
Example #2: KVM doesn't clear the bits when the PMU is disabled, or when
there's no architectural PMU.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20220611005755.753273-3-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions