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: x86: Selftests changes for 6.17
Date: Fri, 25 Jul 2025 15:07:09 -0700 [thread overview]
Message-ID: <20250725220713.264711-10-seanjc@google.com> (raw)
In-Reply-To: <20250725220713.264711-1-seanjc@google.com>
Minor "quality of user life" selftests cleanups.
The following changes since commit 28224ef02b56fceee2c161fe2a49a0bb197e44f5:
KVM: TDX: Report supported optional TDVMCALLs in TDX capabilities (2025-06-20 14:20:20 -0400)
are available in the Git repository at:
https://github.com/kvm-x86/linux.git tags/kvm-x86-selftests-6.17
for you to fetch changes up to 71443210e26de3b35aea8dced894ad3c420d55d5:
KVM: selftests: Print a more helpful message for EACCESS in access tracking test (2025-06-20 13:39:11 -0700)
----------------------------------------------------------------
KVM selftests changes for 6.17
- Fix a comment typo.
- Verify KVM is loaded when getting any KVM module param so that attempting to
run a selftest without kvm.ko loaded results in a SKIP message about KVM not
being loaded/enabled, versus some random parameter not existing.
- SKIP tests that hit EACCES when attempting to access a file, with a "Root
required?" help message. In most cases, the test just needs to be run with
elevated permissions.
----------------------------------------------------------------
Rahul Kumar (1):
KVM: selftests: Fix spelling of 'occurrences' in sparsebit.c comments
Sean Christopherson (4):
KVM: selftests: Verify KVM is loaded when getting a KVM module param
KVM: selftests: Add __open_path_or_exit() variant to provide extra help info
KVM: selftests: Play nice with EACCES errors in open_path_or_exit()
KVM: selftests: Print a more helpful message for EACCESS in access tracking test
.../selftests/kvm/access_tracking_perf_test.c | 7 ++-----
tools/testing/selftests/kvm/include/kvm_util.h | 1 +
.../testing/selftests/kvm/include/x86/processor.h | 6 +++++-
tools/testing/selftests/kvm/lib/kvm_util.c | 23 ++++++++++++++++++----
tools/testing/selftests/kvm/lib/sparsebit.c | 4 ++--
tools/testing/selftests/kvm/lib/x86/processor.c | 10 ----------
.../x86/vmx_exception_with_invalid_guest_state.c | 2 +-
7 files changed, 30 insertions(+), 23 deletions(-)
next prev parent reply other threads:[~2025-07-25 22:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 22:07 [GIT PULL] KVM: x86: Changes " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: x86: Local APIC refactoring " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: Dirty Ring changes " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: Generic " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: IRQ " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: x86: Misc " Sean Christopherson
2025-07-28 15:11 ` Paolo Bonzini
2025-07-25 22:07 ` [GIT PULL] KVM: x86: MMIO State Data mitigation " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: x86: MMU " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: Device assignment accounting " Sean Christopherson
2025-07-28 15:08 ` Paolo Bonzini
2025-07-25 22:07 ` Sean Christopherson [this message]
2025-07-25 22:07 ` [GIT PULL] KVM: x86: SEV " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: x86: SVM " Sean Christopherson
2025-07-25 22:07 ` [GIT PULL] KVM: x86: VMX " Sean Christopherson
2025-07-28 15:47 ` Paolo Bonzini
2025-07-29 19:44 ` Sean Christopherson
2025-07-30 17:55 ` Paolo Bonzini
2025-07-28 15:50 ` [GIT PULL] KVM: x86: Changes " Paolo Bonzini
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=20250725220713.264711-10-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®