From: Like Xu <like.xu.linux@gmail.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Ravi Bangoria <ravi.bangoria@amd.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] KVM: x86/pmu: Hide guest counter updates from the VMRUN instruction
Date: Fri, 10 Mar 2023 18:53:41 +0800 [thread overview]
Message-ID: <20230310105346.12302-1-likexu@tencent.com> (raw)
Hi,
Considering that developers are more likely to have access to AMD VMs
and use vPMU inside guest, there's a dark cloud that needs to rain.
The x86_64/pmu_event_filter_test always fails on Zen3 boxes:
test_amd_deny_list: Branch instructions retired = 43 (expected 42)
test_without_filter: Branch instructions retired = 43 (expected 42)
test_member_allow_list: Branch instructions retired = 43 (expected 42)
test_not_member_deny_list: Branch instructions retired = 43 (expected 42)
,which is not caused by the event_filter feature (otherwise it's zero).
After some dubious guessing and microtesting on Zen3+ pmu hardware,
we found that VMRUN or one of the instructions in __svm_vcpu_run()
causes a guest-only enabled counter for counting guest instruction (in the
pmu_event_filter case, the branch instruction) to always increase by one
right after each vm_entry.
This creates an inconsistency with the AMD64_EVENTSEL_GUESTONLY,
where the vPMU user in the VM does not expect to see any counter
changes due to the SVM transaction at all. This patch set provides a low
overhead software fix until HW change arrives or simply no fix planned.
Prerequisite:
KVM: x86/pmu/misc: Fix a typo on kvm_pmu_request_counter_reprogam()
KVM: x86/pmu: Prevent the PMU from counting disallowed events
Please feel free to run more tests, add more or share comments.
Thanks,
Like Xu (5):
KVM: x86/pmu: Emulate CTR overflow directly in kvm_pmu_handle_event()
KVM: x86/pmu: Add a helper to check if pmc has PEBS mode enabled
KVM: x86/pmu: Move the overflow of a normal counter out of PMI context
KVM: x86/pmu: Reorder functions to reduce unnecessary declarations
KVM: x86/pmu: Hide guest counter updates from the VMRUN instruction
arch/x86/include/asm/kvm_host.h | 4 ++
arch/x86/kvm/pmu.c | 81 +++++++++++++++++++++------------
arch/x86/kvm/pmu.h | 37 +++++++++++++--
arch/x86/kvm/svm/pmu.c | 1 +
arch/x86/kvm/svm/svm.c | 28 ++++++++++++
5 files changed, 119 insertions(+), 32 deletions(-)
base-commit: e79412ef245c53b2157458754327f39f43dd6a49
--
2.39.2
next reply other threads:[~2023-03-10 10:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 10:53 Like Xu [this message]
2023-03-10 10:53 ` [PATCH 1/5] KVM: x86/pmu: Emulate CTR overflow directly in kvm_pmu_handle_event() Like Xu
2023-03-10 10:53 ` [PATCH 2/5] KVM: x86/pmu: Add a helper to check if pmc has PEBS mode enabled Like Xu
2023-05-24 20:54 ` Sean Christopherson
2023-03-10 10:53 ` [PATCH 3/5] KVM: x86/pmu: Move the overflow of a normal counter out of PMI context Like Xu
2023-05-24 21:03 ` Sean Christopherson
2023-03-10 10:53 ` [PATCH 4/5] KVM: x86/pmu: Reorder functions to reduce unnecessary declarations Like Xu
2023-05-24 21:14 ` Sean Christopherson
2023-03-10 10:53 ` [PATCH 5/5] KVM: x86/pmu: Hide guest counter updates from the VMRUN instruction Like Xu
2023-04-07 2:18 ` Sean Christopherson
2023-04-07 8:15 ` Like Xu
2023-04-07 14:56 ` Sean Christopherson
2023-04-19 13:41 ` Like Xu
2023-04-26 5:25 ` Sandipan Das
2023-04-26 6:25 ` Like Xu
2023-05-24 20:41 ` Sean Christopherson
2023-05-24 20:47 ` Jim Mattson
2023-05-24 21:29 ` Sean Christopherson
2023-05-24 21:32 ` Jim Mattson
2023-05-29 14:51 ` Like Xu
2023-05-30 20:00 ` Jim Mattson
2023-05-24 21:23 ` Sean Christopherson
2023-05-24 21:30 ` Jim Mattson
2023-05-29 14:36 ` Like Xu
2023-03-13 10:57 ` [PATCH 0/5] " Sandipan Das
2023-03-23 8:16 ` Like Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230310105346.12302-1-likexu@tencent.com \
--to=like.xu.linux@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=ravi.bangoria@amd.com \
--cc=seanjc@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®