mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Maxim Levitsky <mlevitsk@redhat.com>
Subject: [PATCH v2 0/4] KVM: selftests: Annotate guest printfs as such
Date: Wed, 29 Nov 2023 14:49:12 -0800	[thread overview]
Message-ID: <20231129224916.532431-1-seanjc@google.com> (raw)

Fix a handful of broken guest assert/printf messages, and annotate guest
ucall, printf, and assert helpers with __printf() so that such breakage is
detected by the compiler.

v2:
 - Annotate the relevant helpers. [Maxim]
 - Fix all other warnings (v1 fixed only the MWAIT error message)

v1: https://lore.kernel.org/all/20231107182159.404770-1-seanjc@google.com

Sean Christopherson (4):
  KVM: selftests: Fix MWAIT error message when guest assertion fails
  KVM: selftests: Fix benign %llx vs. %lx issues in guest asserts
  KVM: selftests: Fix broken assert messages in Hyper-V features test
  KVM: selftests: Annotate guest ucall, printf, and assert helpers with
    __printf()

 tools/testing/selftests/kvm/include/test_util.h        |  2 +-
 tools/testing/selftests/kvm/include/ucall_common.h     |  7 ++++---
 tools/testing/selftests/kvm/set_memory_region_test.c   |  6 +++---
 tools/testing/selftests/kvm/x86_64/hyperv_features.c   | 10 +++++-----
 .../testing/selftests/kvm/x86_64/monitor_mwait_test.c  |  6 ++++--
 .../kvm/x86_64/private_mem_conversions_test.c          |  2 +-
 .../selftests/kvm/x86_64/svm_nested_soft_inject_test.c |  4 ++--
 tools/testing/selftests/kvm/x86_64/vmx_pmu_caps_test.c |  2 +-
 tools/testing/selftests/kvm/x86_64/xcr0_cpuid_test.c   |  8 ++++----
 9 files changed, 25 insertions(+), 22 deletions(-)


base-commit: 6803fb00772cc50cd59a66bd8caaee5c84b13fcf
-- 
2.43.0.rc1.413.gea7ed67945-goog


             reply	other threads:[~2023-11-29 22:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 22:49 Sean Christopherson [this message]
2023-11-29 22:49 ` [PATCH v2 1/4] KVM: selftests: Fix MWAIT error message when guest assertion fails Sean Christopherson
2023-11-29 22:49 ` [PATCH v2 2/4] KVM: selftests: Fix benign %llx vs. %lx issues in guest asserts Sean Christopherson
2023-11-29 22:49 ` [PATCH v2 3/4] KVM: selftests: Fix broken assert messages in Hyper-V features test Sean Christopherson
2023-11-29 22:49 ` [PATCH v2 4/4] KVM: selftests: Annotate guest ucall, printf, and assert helpers with __printf() Sean Christopherson
2023-12-01 23:30 ` [PATCH v2 0/4] KVM: selftests: Annotate guest printfs as such 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=20231129224916.532431-1-seanjc@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlevitsk@redhat.com \
    --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®