From: Paolo Bonzini <pbonzini@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [GIT PULL] Final set of (mostly selftests) KVM patches for Linux 6.0
Date: Fri, 30 Sep 2022 21:08:28 +0200 [thread overview]
Message-ID: <20220930190828.116565-1-pbonzini@redhat.com> (raw)
Linus,
The following changes since commit 69604fe76e58c9d195e48b41d019b07fc27ce9d7:
Merge tag 'kvm-s390-master-6.0-2' of https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into HEAD (2022-09-23 10:06:08 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus-6.0
for you to fetch changes up to 07834cc4df06d48a354bb0b1eb1b07069584e581:
KVM: selftests: Compare insn opcodes directly in fix_hypercall_test (2022-09-29 12:54:02 -0400)
----------------------------------------------------------------
A small fix to the reported set of supported CPUID bits, and selftests fixes:
* Skip tests that require EPT when it is not available
* Do not hang when a test fails with an empty stack trace
* avoid spurious failure when running access_tracking_perf_test in a KVM guest
* work around GCC's tendency to optimize loops into mem*() functions, which
breaks because the guest code in selftests cannot call into PLTs
* fix -Warray-bounds error in fix_hypercall_test
----------------------------------------------------------------
David Matlack (2):
KVM: selftests: Skip tests that require EPT when it is not available
KVM: selftests: Gracefully handle empty stack traces
Emanuele Giuseppe Esposito (1):
KVM: selftests: replace assertion with warning in access_tracking_perf_test
Jim Mattson (1):
KVM: x86: Hide IA32_PLATFORM_DCA_CAP[31:0] from the guest
Sean Christopherson (2):
KVM: selftests: Implement memcmp(), memcpy(), and memset() for guest use
KVM: selftests: Compare insn opcodes directly in fix_hypercall_test
arch/x86/kvm/cpuid.c | 2 --
tools/testing/selftests/kvm/Makefile | 11 +++++-
.../selftests/kvm/access_tracking_perf_test.c | 25 +++++++++-----
tools/testing/selftests/kvm/include/x86_64/vmx.h | 1 +
tools/testing/selftests/kvm/lib/assert.c | 20 +++++++----
tools/testing/selftests/kvm/lib/string_override.c | 39 ++++++++++++++++++++++
tools/testing/selftests/kvm/lib/x86_64/vmx.c | 20 +++++++++++
.../selftests/kvm/x86_64/fix_hypercall_test.c | 34 +++++++++----------
8 files changed, 115 insertions(+), 37 deletions(-)
create mode 100644 tools/testing/selftests/kvm/lib/string_override.c
reply other threads:[~2022-09-30 19:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220930190828.116565-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.