From: Mingwei Zhang <mizhang@google.com>
To: kernel test robot <lkp@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kbuild-all@lists.01.org, kvm <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Sean Christopherson <seanjc@google.com>,
David Matlack <dmatlack@google.com>,
Jing Zhang <jingzhangos@google.com>, Peter Xu <peterx@redhat.com>,
Ben Gardon <bgardon@google.com>
Subject: Re: [PATCH v2 2/2] selftests: KVM: use dirty logging to check if page stats work correctly
Date: Sun, 29 Aug 2021 21:42:13 -0700 [thread overview]
Message-ID: <CAL715WJvYLyWS1dY_-69WEfp5HnTfCFrPNpx0OX1eOqN8D5DeA@mail.gmail.com> (raw)
In-Reply-To: <202108301131.HmLTqoX4-lkp@intel.com>
> dirty_log_perf_test.c: In function 'run_test':
> >> dirty_log_perf_test.c:236:28: error: macro "TEST_ASSERT" requires 3 arguments, but only 1 given
> 236 | "2M page number is zero");
> | ^
> In file included from include/kvm_util.h:10,
> from dirty_log_perf_test.c:17:
> include/test_util.h:46: note: macro "TEST_ASSERT" defined here
> 46 | #define TEST_ASSERT(e, fmt, ...) \
> |
> >> dirty_log_perf_test.c:235:3: error: 'TEST_ASSERT' undeclared (first use in this function)
> 235 | TEST_ASSERT(get_page_stats(X86_PAGE_SIZE_2M) > 0
> | ^~~~~~~~~~~
> dirty_log_perf_test.c:235:3: note: each undeclared identifier is reported only once for each function it appears in
>
Sorry, there is one fix not checked in before I sent it out. Will fix
it in the next version.
prev parent reply other threads:[~2021-08-30 4:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 18:26 [PATCH v2 0/2] selftests: verify page stats in kvm x86/mmu Mingwei Zhang
2021-08-29 18:26 ` [PATCH v2 1/2] selftests: KVM: align guest physical memory base address to 1GB Mingwei Zhang
2021-08-31 16:54 ` Sean Christopherson
2021-09-06 19:56 ` Mingwei Zhang
2021-08-29 18:26 ` [PATCH v2 2/2] selftests: KVM: use dirty logging to check if page stats work correctly Mingwei Zhang
2021-08-30 4:02 ` kernel test robot
2021-08-30 4:42 ` Mingwei Zhang [this message]
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=CAL715WJvYLyWS1dY_-69WEfp5HnTfCFrPNpx0OX1eOqN8D5DeA@mail.gmail.com \
--to=mizhang@google.com \
--cc=bgardon@google.com \
--cc=dmatlack@google.com \
--cc=jingzhangos@google.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=seanjc@google.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;
as well as URLs for NNTP newsgroup(s).