From: Peter Xu <peterx@redhat.com>
To: Avihai Horon <avihaih@nvidia.com>
Cc: qemu-devel@nongnu.org,
"Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
"Juan Quintela" <quintela@redhat.com>,
"Leonardo Bras" <leobras@redhat.com>,
"Yanghang Liu" <yanghliu@redhat.com>
Subject: Re: [PATCH 1/6] migration: Add migration prefix to functions in target.c
Date: Tue, 29 Aug 2023 10:04:42 -0400 [thread overview]
Message-ID: <ZO36+h2p/X/LCG5B@x1n> (raw)
In-Reply-To: <20230828151842.11303-2-avihaih@nvidia.com>
On Mon, Aug 28, 2023 at 06:18:37PM +0300, Avihai Horon wrote:
> The functions in target.c are not static, yet they don't have a proper
> migration prefix. Add such prefix.
>
> Signed-off-by: Avihai Horon <avihaih@nvidia.com>
No issue on the patch itself, but just noticed that we have hard-coded vfio
calls in migration paths.. that's slightly unfortunate. :(
> ---
> migration/migration.h | 4 ++--
> migration/migration.c | 6 +++---
> migration/savevm.c | 2 +-
> migration/target.c | 8 ++++----
> 4 files changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/migration/migration.h b/migration/migration.h
> index 6eea18db36..c5695de214 100644
> --- a/migration/migration.h
> +++ b/migration/migration.h
> @@ -512,8 +512,8 @@ void migration_consume_urgent_request(void);
> bool migration_rate_limit(void);
> void migration_cancel(const Error *error);
>
> -void populate_vfio_info(MigrationInfo *info);
> -void reset_vfio_bytes_transferred(void);
> +void migration_populate_vfio_info(MigrationInfo *info);
> +void migration_reset_vfio_bytes_transferred(void);
> void postcopy_temp_page_reset(PostcopyTmpPage *tmp_page);
>
> #endif
> diff --git a/migration/migration.c b/migration/migration.c
> index 5528acb65e..92866a8f49 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -1039,7 +1039,7 @@ static void fill_source_migration_info(MigrationInfo *info)
> populate_time_info(info, s);
> populate_ram_info(info, s);
> populate_disk_info(info);
> - populate_vfio_info(info);
> + migration_populate_vfio_info(info);
(maybe in the future we should have SaveVMHandlers hooks for populating
data for ram/disk/vfio/..., or some other way to not hard-code these)
> break;
> case MIGRATION_STATUS_COLO:
> info->has_status = true;
> @@ -1048,7 +1048,7 @@ static void fill_source_migration_info(MigrationInfo *info)
> case MIGRATION_STATUS_COMPLETED:
> populate_time_info(info, s);
> populate_ram_info(info, s);
> - populate_vfio_info(info);
> + migration_populate_vfio_info(info);
> break;
> case MIGRATION_STATUS_FAILED:
> info->has_status = true;
> @@ -1641,7 +1641,7 @@ static bool migrate_prepare(MigrationState *s, bool blk, bool blk_inc,
> */
> memset(&mig_stats, 0, sizeof(mig_stats));
> memset(&compression_counters, 0, sizeof(compression_counters));
> - reset_vfio_bytes_transferred();
> + migration_reset_vfio_bytes_transferred();
Could this already be done during vfio_save_setup(), to avoid calling an
vfio function directly in migration.c?
Again, not a request for this patchset, but more to see whether it'll work
to be moved there.
Thanks,
>
> return true;
> }
--
Peter Xu
next prev parent reply other threads:[~2023-08-29 14:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 15:18 [PATCH 0/6] vfio/migration: Block VFIO migration with postcopy and background snapshot Avihai Horon
2023-08-28 15:18 ` [PATCH 1/6] migration: Add migration prefix to functions in target.c Avihai Horon
2023-08-29 13:23 ` Cédric Le Goater
2023-08-29 14:04 ` Peter Xu [this message]
2023-08-29 15:59 ` Avihai Horon
2023-08-28 15:18 ` [PATCH 2/6] vfio/migration: Fail adding device with enable-migration=on and existing blocker Avihai Horon
2023-08-29 13:23 ` Cédric Le Goater
2023-08-28 15:18 ` [PATCH 3/6] vfio/migration: Add vfio_migratable_devices_num() Avihai Horon
2023-08-29 13:24 ` Cédric Le Goater
2023-08-28 15:18 ` [PATCH 4/6] vfio/migration: Change vfio_mig_active() semantics Avihai Horon
2023-08-28 15:18 ` [PATCH 5/6] vfio/migration: Block VFIO migration with postcopy migration Avihai Horon
2023-08-29 13:24 ` Cédric Le Goater
2023-08-29 15:52 ` Avihai Horon
2023-08-29 14:53 ` Peter Xu
2023-08-29 16:20 ` Avihai Horon
2023-08-29 18:27 ` Peter Xu
2023-08-30 7:01 ` Avihai Horon
2023-08-30 8:37 ` Cédric Le Goater
2023-08-30 9:21 ` Avihai Horon
2023-08-30 9:53 ` Cédric Le Goater
2023-08-30 10:12 ` Avihai Horon
2023-08-30 11:17 ` Cédric Le Goater
2023-08-30 14:22 ` Peter Xu
2023-08-30 16:06 ` Avihai Horon
2023-08-28 15:18 ` [PATCH 6/6] vfio/migration: Block VFIO migration with background snapshot Avihai Horon
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=ZO36+h2p/X/LCG5B@x1n \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=clg@redhat.com \
--cc=leobras@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yanghliu@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;
as well as URLs for NNTP newsgroup(s).