public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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.18
Date: Fri, 26 Sep 2025 23:09:04 -0700	[thread overview]
Message-ID: <20250927060910.2933942-5-seanjc@google.com> (raw)
In-Reply-To: <20250927060910.2933942-1-seanjc@google.com>

A mix of fixes, cleanups and new coverage.  Note, there's also a large-ish new
MSR selftest coming in through the "cet" pull request.

The following changes since commit c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9:

  Linux 6.17-rc2 (2025-08-17 15:22:10 -0700)

are available in the Git repository at:

  https://github.com/kvm-x86/linux.git tags/kvm-x86-selftests-6.18

for you to fetch changes up to df1f294013da715f32521b3d0a69773e660a1af5:

  KVM: selftests: Add ex_str() to print human friendly name of exception vectors (2025-09-23 08:39:02 -0700)

----------------------------------------------------------------
KVM selftests changes for 6.18

 - Add #DE coverage in the fastops test (the only exception that's guest-
   triggerable in fastop-emulated instructions).

 - Fix PMU selftests errors encountered on Granite Rapids (GNR), Sierra
   Forest (SRF) and Clearwater Forest (CWF).

 - Minor cleanups and improvements

----------------------------------------------------------------
Alok Tiwari (1):
      KVM: selftests: Fix typo in hyperv cpuid test message

Dapeng Mi (2):
      KVM: selftests: Add timing_info bit support in vmx_pmu_caps_test
      KVM: selftests: Validate more arch-events in pmu_counters_test

Gopi Krishna Menon (1):
      KVM: selftests: fix minor typo in cpumodel_subfuncs

James Houghton (1):
      KVM: selftests: Fix signedness issue with vCPU mmap size check

Sean Christopherson (8):
      KVM: selftests: Move Intel and AMD module param helpers to x86/processor.h
      KVM: selftests: Add support for #DE exception fixup
      KVM: selftests: Add coverage for 'b' (byte) sized fastops emulation
      KVM: selftests: Dedup the gnarly constraints of the fastops tests (more macros!)
      KVM: selftests: Add support for DIV and IDIV in the fastops test
      KVM: selftests: Track unavailable_mask for PMU events as 32-bit value
      KVM: selftests: Reduce number of "unavailable PMU events" combos tested
      KVM: selftests: Add ex_str() to print human friendly name of exception vectors

Sukrut Heroorkar (1):
      selftests/kvm: remove stale TODO in xapic_state_test

dongsheng (1):
      KVM: selftests: Handle Intel Atom errata that leads to PMU event overcount

 tools/testing/selftests/kvm/include/kvm_util.h     | 17 +++--
 tools/testing/selftests/kvm/include/x86/pmu.h      | 26 +++++++
 .../testing/selftests/kvm/include/x86/processor.h  | 35 ++++++++-
 tools/testing/selftests/kvm/lib/kvm_util.c         | 42 ++---------
 tools/testing/selftests/kvm/lib/x86/pmu.c          | 49 +++++++++++++
 tools/testing/selftests/kvm/lib/x86/processor.c    | 39 +++++++++-
 .../selftests/kvm/s390/cpumodel_subfuncs_test.c    |  2 +-
 tools/testing/selftests/kvm/x86/fastops_test.c     | 82 +++++++++++++++++-----
 tools/testing/selftests/kvm/x86/hyperv_cpuid.c     |  2 +-
 tools/testing/selftests/kvm/x86/hyperv_features.c  | 16 ++---
 .../testing/selftests/kvm/x86/monitor_mwait_test.c |  8 +--
 .../testing/selftests/kvm/x86/pmu_counters_test.c  | 67 ++++++++++++------
 .../selftests/kvm/x86/pmu_event_filter_test.c      |  4 +-
 .../testing/selftests/kvm/x86/vmx_pmu_caps_test.c  |  7 +-
 tools/testing/selftests/kvm/x86/xapic_state_test.c |  4 +-
 tools/testing/selftests/kvm/x86/xcr0_cpuid_test.c  | 12 ++--
 16 files changed, 303 insertions(+), 109 deletions(-)

  parent reply	other threads:[~2025-09-27  6:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-27  6:09 [GIT PULL] KVM: x86 pull requests 6.18 Sean Christopherson
2025-09-27  6:09 ` [GIT PULL] x86/kvm: Guest side changes for 6.18 Sean Christopherson
2025-09-30 17:28   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: One lone common change " Sean Christopherson
2025-09-30 17:28   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: MMU changes " Sean Christopherson
2025-09-30 17:33   ` Paolo Bonzini
2025-09-27  6:09 ` Sean Christopherson [this message]
2025-09-30 17:24   ` [GIT PULL] KVM: Selftests " Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2025-09-30 17:33   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2025-09-30 17:35   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: SNP CipherTextHiding " Sean Christopherson
2025-09-30 17:35   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: Misc changes " Sean Christopherson
2025-09-30 18:06   ` Paolo Bonzini
2025-09-27  6:09 ` [GIT PULL] KVM: x86: CET virtualization " Sean Christopherson
2025-09-27  6:09 ` [GIT PULL] KVM: Symbol export restrictions " Sean Christopherson
2025-09-30 17:41   ` Paolo Bonzini
2025-09-30 18:10 ` [GIT PULL] KVM: x86 pull requests 6.18 Paolo Bonzini
2025-09-30 19:16   ` 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=20250927060910.2933942-5-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