From: Thomas Huth <thuth@redhat.com>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Leonardo Bras Soares Passos <lsoaresp@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH] tests: Fix migration-test build failure for sparc
Date: Thu, 29 Jul 2021 07:55:15 +0200 [thread overview]
Message-ID: <d5093e20-fb32-dcd5-2100-b26eafb55672@redhat.com> (raw)
In-Reply-To: <20210728214128.206198-1-peterx@redhat.com>
On 28/07/2021 23.41, Peter Xu wrote:
> Even if <linux/kvm.h> seems to exist for all archs on linux, however including
> it with __linux__ defined seems to be not working yet as it'll try to include
> asm/kvm.h and that can be missing for archs that do not support kvm.
>
> To fix this (instead of any attempt to fix linux headers..), we can mark the
> header to be x86_64 only, because it's so far only service for adding the kvm
> dirty ring test.
>
> No need to have "Fixes" as the issue is just introduced very recently.
>
> Reported-by: Richard Henderson <rth@twiddle.net>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
> tests/qtest/migration-test.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c
> index 1e8b7784ef..cc5e83d98a 100644
> --- a/tests/qtest/migration-test.c
> +++ b/tests/qtest/migration-test.c
> @@ -27,7 +27,8 @@
> #include "migration-helpers.h"
> #include "tests/migration/migration-test.h"
>
> -#if defined(__linux__)
> +/* For dirty ring test; so far only x86_64 is supported */
> +#if defined(__linux__) && defined(HOST_X86_64)
> #include "linux/kvm.h"
> #endif
>
> @@ -1395,7 +1396,7 @@ static void test_multifd_tcp_cancel(void)
>
> static bool kvm_dirty_ring_supported(void)
> {
> -#if defined(__linux__)
> +#if defined(__linux__) && defined(HOST_X86_64)
> int ret, kvm_fd = open("/dev/kvm", O_RDONLY);
>
> if (kvm_fd < 0) {
>
Acked-by: Thomas Huth <thuth@redhat.com>
Juan, Dave, if you don't mind I can take this through my testing branch -
I'm planning to send a pull request today anyway.
Thomas
next prev parent reply other threads:[~2021-07-29 5:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 21:41 [PATCH] tests: Fix migration-test build failure for sparc Peter Xu
2021-07-28 22:02 ` Peter Xu
2021-07-28 23:05 ` Richard Henderson
2021-07-28 23:48 ` Philippe Mathieu-Daudé
2021-07-29 15:39 ` Peter Xu
2021-07-29 5:55 ` Thomas Huth [this message]
2021-07-29 8:26 ` Dr. David Alan Gilbert
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=d5093e20-fb32-dcd5-2100-b26eafb55672@redhat.com \
--to=thuth@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lsoaresp@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
/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).