From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: [PATCH 0/2] KVM: selftests: Fix PMU counters test flakiness
Date: Thu, 27 Jun 2024 17:55:55 -0700 [thread overview]
Message-ID: <20240628005558.3835480-1-seanjc@google.com> (raw)
v2 of Maxim's patch to fix the flakiness with the PMU counters test do to
a single CLFLUSH not guaranteeing an LLC miss.
v2:
- Add a prep patch to tweak the macros in preparation for moving CLFUSH{,OPT}
into the loop.
- Keep the MFENCE (because paranoia doesn't hurt in this case).
v1: https://lore.kernel.org/all/20240621204305.1730677-1-mlevitsk@redhat.com
Maxim Levitsky (1):
KVM: selftests: Increase robustness of LLC cache misses in PMU
counters test
Sean Christopherson (1):
KVM: selftests: Rework macros in PMU counters test to prep for
multi-insn loop
.../selftests/kvm/x86_64/pmu_counters_test.c | 44 ++++++++++++-------
1 file changed, 29 insertions(+), 15 deletions(-)
base-commit: c81b138d5075c6f5ba3419ac1d2a2e7047719c14
--
2.45.2.803.g4e1b14247a-goog
next reply other threads:[~2024-06-28 0:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 0:55 Sean Christopherson [this message]
2024-06-28 0:55 ` [PATCH 1/2] KVM: selftests: Rework macros in PMU counters test to prep for multi-insn loop Sean Christopherson
2024-06-28 0:55 ` [PATCH 2/2] KVM: selftests: Increase robustness of LLC cache misses in PMU counters test Sean Christopherson
2024-06-28 22:55 ` [PATCH 0/2] KVM: selftests: Fix PMU counters test flakiness Sean Christopherson
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=20240628005558.3835480-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.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®