From: Andrew Jones <drjones@redhat.com>
To: Colton Lewis <coltonlewis@google.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
pbonzini@redhat.com, seanjc@google.com, vkuznets@redhat.com,
thuth@redhat.com, maz@kernel.org
Subject: Re: [PATCH 3/4] KVM: selftests: Write REPORT_GUEST_ASSERT macros to pair with GUEST_ASSERT
Date: Thu, 16 Jun 2022 14:46:09 +0200 [thread overview]
Message-ID: <20220616124609.fforgaccsp3rwbxi@gator> (raw)
In-Reply-To: <20220615193116.806312-4-coltonlewis@google.com>
On Wed, Jun 15, 2022 at 07:31:15PM +0000, Colton Lewis wrote:
> Write REPORT_GUEST_ASSERT macros to pair with GUEST_ASSERT to abstract
> and make consistent all guest assertion reporting. Every report
> includes an explanatory string, a filename, and a line number.
>
> Signed-off-by: Colton Lewis <coltonlewis@google.com>
> ---
> .../selftests/kvm/include/ucall_common.h | 42 +++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/tools/testing/selftests/kvm/include/ucall_common.h b/tools/testing/selftests/kvm/include/ucall_common.h
> index 568c562f14cd..e8af3b4fef6d 100644
> --- a/tools/testing/selftests/kvm/include/ucall_common.h
> +++ b/tools/testing/selftests/kvm/include/ucall_common.h
> @@ -6,6 +6,7 @@
> */
> #ifndef SELFTEST_KVM_UCALL_COMMON_H
> #define SELFTEST_KVM_UCALL_COMMON_H
> +#include "test_util.h"
>
> /* Common ucalls */
> enum {
> @@ -64,4 +65,45 @@ enum guest_assert_builtin_args {
>
> #define GUEST_ASSERT_EQ(a, b) __GUEST_ASSERT((a) == (b), #a " == " #b, 2, a, b)
>
> +#define __REPORT_GUEST_ASSERT(_ucall, fmt, _args...) \
> + TEST_FAIL("%s at %s:%ld\n" fmt, \
> + (const char *)(_ucall).args[GUEST_ERROR_STRING], \
> + (const char *)(_ucall).args[GUEST_FILE], \
> + (_ucall).args[GUEST_LINE], \
> + ##_args)
> +
> +#define GUEST_ASSERT_ARG(ucall, i) ((ucall).args[GUEST_ASSERT_BUILTIN_NARGS + i])
> +
> +#define REPORT_GUEST_ASSERT(ucall) \
> + __REPORT_GUEST_ASSERT((ucall), "")
> +
> +#define REPORT_GUEST_ASSERT_1(ucall, fmt) \
> + __REPORT_GUEST_ASSERT((ucall), \
> + fmt, \
> + GUEST_ASSERT_ARG((ucall), 0))
> +
> +#define REPORT_GUEST_ASSERT_2(ucall, fmt) \
> + __REPORT_GUEST_ASSERT((ucall), \
> + fmt, \
> + GUEST_ASSERT_ARG((ucall), 0), \
> + GUEST_ASSERT_ARG((ucall), 1))
> +
> +#define REPORT_GUEST_ASSERT_3(ucall, fmt) \
> + __REPORT_GUEST_ASSERT((ucall), \
> + fmt, \
> + GUEST_ASSERT_ARG((ucall), 0), \
> + GUEST_ASSERT_ARG((ucall), 1), \
> + GUEST_ASSERT_ARG((ucall), 2))
> +
> +#define REPORT_GUEST_ASSERT_4(ucall, fmt) \
> + __REPORT_GUEST_ASSERT((ucall), \
> + fmt, \
> + GUEST_ASSERT_ARG((ucall), 0), \
> + GUEST_ASSERT_ARG((ucall), 1), \
> + GUEST_ASSERT_ARG((ucall), 2), \
> + GUEST_ASSERT_ARG((ucall), 3))
> +
> +#define REPORT_GUEST_ASSERT_N(ucall, fmt, args...) \
> + __REPORT_GUEST_ASSERT((ucall), fmt, ##args)
> +
> #endif /* SELFTEST_KVM_UCALL_COMMON_H */
> --
> 2.36.1.476.g0c4daa206d-goog
>
nit: All the ()'s around ucall when it's between ( and , are unnecessary.
Otherwise,
Reviewed-by: Andrew Jones <drjones@redhat.com>
Thanks,
drew
next prev parent reply other threads:[~2022-06-16 12:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 19:31 [PATCH 0/4] Fix filename reporting in guest asserts Colton Lewis
2022-06-15 19:31 ` [PATCH 1/4] KVM: selftests: enumerate GUEST_ASSERT arguments Colton Lewis
2022-06-16 12:47 ` Andrew Jones
2022-06-15 19:31 ` [PATCH 2/4] KVM: selftests: Increase UCALL_MAX_ARGS to 7 Colton Lewis
2022-06-16 12:10 ` Andrew Jones
2022-06-17 17:05 ` Colton Lewis
2022-06-18 0:09 ` Sean Christopherson
2022-06-20 7:21 ` Andrew Jones
2022-06-20 8:59 ` Anup Patel
2022-06-20 13:20 ` Andrew Jones
2022-06-20 13:21 ` Andrew Jones
2022-06-15 19:31 ` [PATCH 3/4] KVM: selftests: Write REPORT_GUEST_ASSERT macros to pair with GUEST_ASSERT Colton Lewis
2022-06-16 12:46 ` Andrew Jones [this message]
2022-06-15 19:31 ` [PATCH 4/4] KVM: selftests: Fix filename reporting in guest asserts Colton Lewis
2022-06-16 12:45 ` Andrew Jones
2022-06-20 12:04 ` Paolo Bonzini
2022-07-06 15:29 ` Colton Lewis
2022-07-07 6:39 ` Andrew Jones
2022-07-20 17:42 ` [PATCH 0/4] " 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=20220616124609.fforgaccsp3rwbxi@gator \
--to=drjones@redhat.com \
--cc=coltonlewis@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=thuth@redhat.com \
--cc=vkuznets@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