mirror of https://lore.kernel.org/lkml/
 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: x86: Selftests fixes for 6.6
Date: Fri, 13 Oct 2023 16:48:08 -0700	[thread overview]
Message-ID: <20231013234808.1115781-2-seanjc@google.com> (raw)
In-Reply-To: <20231013234808.1115781-1-seanjc@google.com>

Please pull a fix, a cleanup, and a workaround for 6.6.  The guest printf change
really should go into 6.6, as it fixes an issue introduced in 6.6 that causes
affected guest asserts to print garbage.  The other two changes are much less
urgent, but I couldn't think of a any reason to hold them back.

The following changes since commit 5804c19b80bf625c6a9925317f845e497434d6d3:

  Merge tag 'kvm-riscv-fixes-6.6-1' of https://github.com/kvm-riscv/linux into HEAD (2023-09-23 05:35:55 -0400)

are available in the Git repository at:

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

for you to fetch changes up to 6313e096dbfaf1377ba8f5f8ccd720cc36c576c6:

  KVM: selftests: Zero-initialize entire test_result in memslot perf test (2023-10-05 19:23:47 -0700)

----------------------------------------------------------------
KVM selftests fixes for 6.6:

 - Play nice with %llx when formatting guest printf and assert statements.

 - Clean up stale test metadata.

 - Zero-initialize structures in memslot perf test to workaround a suspected
   "may be used uninitialized" false positives from GCC.

----------------------------------------------------------------
Like Xu (1):
      KVM: selftests: Remove obsolete and incorrect test case metadata

Sean Christopherson (2):
      KVM: selftests: Treat %llx like %lx when formatting guest printf
      KVM: selftests: Zero-initialize entire test_result in memslot perf test

 tools/testing/selftests/kvm/include/ucall_common.h       | 2 --
 tools/testing/selftests/kvm/lib/guest_sprintf.c          | 7 +++++++
 tools/testing/selftests/kvm/lib/x86_64/apic.c            | 2 --
 tools/testing/selftests/kvm/memslot_perf_test.c          | 9 +++------
 tools/testing/selftests/kvm/x86_64/hyperv_svm_test.c     | 2 --
 tools/testing/selftests/kvm/x86_64/nx_huge_pages_test.c  | 2 --
 tools/testing/selftests/kvm/x86_64/nx_huge_pages_test.sh | 1 -
 tools/testing/selftests/kvm/x86_64/tsc_scaling_sync.c    | 4 ----
 tools/testing/selftests/kvm/x86_64/xen_shinfo_test.c     | 4 ----
 9 files changed, 10 insertions(+), 23 deletions(-)

  reply	other threads:[~2023-10-13 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 23:48 [GIT PULL] KVM: x86: PMU " Sean Christopherson
2023-10-13 23:48 ` Sean Christopherson [this message]
2023-10-15 12:25   ` [GIT PULL] KVM: x86: Selftests " Paolo Bonzini
2023-10-15 12:24 ` [GIT PULL] KVM: x86: PMU " 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=20231013234808.1115781-2-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®