All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, Thomas Huth <thuth@redhat.com>,
	Jared Rossi <jrossi@linux.ibm.com>,
	Laurent Vivier <lvivier@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Cornelia Huck <cohuck@redhat.com>,
	Eric Farman <farman@linux.ibm.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>
Subject: Re: [PATCH v1] tests/qtest/migration: Fix A-B file build
Date: Tue, 5 May 2026 12:44:25 -0400	[thread overview]
Message-ID: <afoeaRAxWSMO_gK5@x1.local> (raw)
In-Reply-To: <20260429231025.30818-1-farosas@suse.de>

On Wed, Apr 29, 2026 at 08:10:25PM -0300, Fabiano Rosas wrote:
> diff --git a/tests/qtest/migration/bootfile.h b/tests/qtest/migration/bootfile.h
> index 96e784b163..0ce5b34433 100644
> --- a/tests/qtest/migration/bootfile.h
> +++ b/tests/qtest/migration/bootfile.h
> @@ -8,6 +8,15 @@
>  #ifndef BOOTFILE_H
>  #define BOOTFILE_H
>  
> +/*
> + * This file is included from qtest, but also from the assembly code
> + * that generates the header file containing the guest workload. Don't
> + * expose the function declarations and non-standard types to it.
> + */
> +#ifdef __ASSEMBLER__
> +#define MIGRATION_GUEST_CODE
> +#endif

Just to mention: this triggers a checkpatch warning (I only notice this
when running checkpatch locally; CI is fine with warnings), which seems to
be false positive.

But still, I wonder whether we need this at all. IIUC we can also put those
into a separate smaller header and include that here, then use that one for
arch a-b-bios builds.

Even if it will work, we can leave it for later.

> +
>  /* Common */
>  #define TEST_MEM_PAGE_SIZE 4096
>  
> @@ -33,8 +42,10 @@
>   */
>  #define ARM_TEST_MAX_KERNEL_SIZE (512 * 1024)
>  
> +#ifndef MIGRATION_GUEST_CODE
>  void bootfile_delete(void);
>  char *bootfile_create(const char *arch, const char *dir, bool suspend_me);
>  char *bootfile_get(void);
> +#endif

-- 
Peter Xu



  parent reply	other threads:[~2026-05-05 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 23:10 [PATCH v1] tests/qtest/migration: Fix A-B file build Fabiano Rosas
2026-05-05 16:32 ` Peter Xu
2026-05-05 19:53   ` Matthew Rosato
2026-05-05 16:44 ` Peter Xu [this message]
2026-05-05 19:11   ` Fabiano Rosas
2026-05-05 19:38     ` Peter Xu

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=afoeaRAxWSMO_gK5@x1.local \
    --to=peterx@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=farosas@suse.de \
    --cc=jrossi@linux.ibm.com \
    --cc=lvivier@redhat.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.