From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>
Subject: [GIT PULL] KVM: Selftests changes for 6.11
Date: Fri, 12 Jul 2024 16:56:57 -0700 [thread overview]
Message-ID: <20240712235701.1458888-8-seanjc@google.com> (raw)
In-Reply-To: <20240712235701.1458888-1-seanjc@google.com>
A handful of random selftests changes. Props to Maxim for figuring out a way
to fix the PMU counters test.
The following changes since commit c3f38fa61af77b49866b006939479069cd451173:
Linux 6.10-rc2 (2024-06-02 15:44:56 -0700)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-selftests-6.11
for you to fetch changes up to 4669de42aa6c78669975d58c92433cdedeb7c2c3:
KVM: selftests: Increase robustness of LLC cache misses in PMU counters test (2024-06-28 08:44:03 -0700)
----------------------------------------------------------------
KVM selftests for 6.11
- Remove dead code in the memslot modification stress test.
- Treat "branch instructions retired" as supported on all AMD Family 17h+ CPUs.
- Print the guest pseudo-RNG seed only when it changes, to avoid spamming the
log for tests that create lots of VMs.
- Make the PMU counters test less flaky when counting LLC cache misses by
doing CLFLUSH{OPT} in every loop iteration.
----------------------------------------------------------------
Dr. David Alan Gilbert (1):
KVM: selftests: remove unused struct 'memslot_antagonist_args'
Manali Shukla (1):
KVM: selftests: Treat AMD Family 17h+ as supporting branch insns retired
Maxim Levitsky (1):
KVM: selftests: Increase robustness of LLC cache misses in PMU counters test
Sean Christopherson (2):
KVM: selftests: Print the seed for the guest pRNG iff it has changed
KVM: selftests: Rework macros in PMU counters test to prep for multi-insn loop
tools/testing/selftests/kvm/lib/kvm_util.c | 9 ++++-
.../kvm/memslot_modification_stress_test.c | 6 ---
.../selftests/kvm/x86_64/pmu_counters_test.c | 44 ++++++++++++++--------
.../selftests/kvm/x86_64/pmu_event_filter_test.c | 35 +++--------------
4 files changed, 41 insertions(+), 53 deletions(-)
next prev parent reply other threads:[~2024-07-12 23:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 23:56 [GIT PULL] KVM: x86 pull requests " Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: Single Xen fix for 6.10 or 6.11 Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: Generic changes for 6.11 Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: Remove MTRR virtualization Sean Christopherson
2024-07-12 23:56 ` [GIT PULL] KVM: x86: PMU changes for 6.11 Sean Christopherson
2024-07-12 23:56 ` Sean Christopherson [this message]
2024-07-12 23:56 ` [GIT PULL (sort of)] KVM: x86: Static call " Sean Christopherson
2024-07-16 14:16 ` Paolo Bonzini
2024-07-16 15:46 ` Sean Christopherson
2024-07-17 5:52 ` Paolo Bonzini
2024-07-12 23:56 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2024-07-12 23:57 ` [GIT PULL] KVM: x86: VMX " 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=20240712235701.1458888-8-seanjc@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®