From: "Cédric Le Goater" <clg@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: Avihai Horon <avihaih@nvidia.com>,
Fabiano Rosas <farosas@suse.de>,
Alex Williamson <alex.williamson@redhat.com>,
"Maciej S . Szmigiero" <maciej.szmigiero@oracle.com>,
Pierrick Bouvier <pierrick.bouvier@linaro.org>,
Anton Johansson <anjo@rev.ng>, Zhao Liu <zhao1.liu@intel.com>,
Luc Michel <luc.michel@amd.com>
Subject: Re: [PATCH] hw/vfio/helpers: Check base architecture at runtime
Date: Tue, 21 Oct 2025 09:05:48 +0200 [thread overview]
Message-ID: <1892476d-6176-4a49-92c9-bae0d0c3a0ba@redhat.com> (raw)
In-Reply-To: <20251020222315.68963-1-philmd@linaro.org>
On 10/21/25 00:23, Philippe Mathieu-Daudé wrote:
> Replace the compile time check of the TARGET_ARM definition
> by a runtime call to target_base_arm().
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> Based-on: <20251020220941.65269-1-philmd@linaro.org>
> ---
> hw/vfio/helpers.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/hw/vfio/helpers.c b/hw/vfio/helpers.c
> index 23d13e5db5f..007c37b28b8 100644
> --- a/hw/vfio/helpers.c
> +++ b/hw/vfio/helpers.c
> @@ -20,6 +20,7 @@
> */
>
> #include "qemu/osdep.h"
> +#include "qemu/target-info.h"
> #include <sys/ioctl.h>
>
> #include "system/kvm.h"
> @@ -220,9 +221,5 @@ bool vfio_arch_wants_loading_config_after_iter(void)
> * See commit d329f5032e17 ("vfio: Move the saving of the config space to
> * the right place in VFIO migration").
> */
> -#if defined(TARGET_ARM)
> - return true;
> -#else
> - return false;
> -#endif
> + return target_base_arm();
is that a new helper ? I don't see it being used anywhere else.
Thanks,
C.
next prev parent reply other threads:[~2025-10-21 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 22:23 [PATCH] hw/vfio/helpers: Check base architecture at runtime Philippe Mathieu-Daudé
2025-10-20 23:01 ` Pierrick Bouvier
2025-10-21 7:05 ` Cédric Le Goater [this message]
2025-10-21 7:56 ` Philippe Mathieu-Daudé
2025-10-21 15:24 ` Maciej S. Szmigiero
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=1892476d-6176-4a49-92c9-bae0d0c3a0ba@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=anjo@rev.ng \
--cc=avihaih@nvidia.com \
--cc=farosas@suse.de \
--cc=luc.michel@amd.com \
--cc=maciej.szmigiero@oracle.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=zhao1.liu@intel.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).