QEMU-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: peterx@redhat.com, Akash Kulhalli <akulhall@redhat.com>,
	Juraj Marcin <jmarcin@redhat.com>
Subject: Re: [PATCH v2 2/7] migration: Add two more trace points for incoming channel mgmt
Date: Wed, 14 Oct 2026 18:50:08 -0300	[thread overview]
Message-ID: <87ecdslzov.fsf@suse.de> (raw)
In-Reply-To: <20261006182046.3767283-3-peterx@redhat.com>

Peter Xu <peterx@redhat.com> writes:

> We have trace points for both multifd channel and preempt channel when a
> new channel is established on the destination, but no main channel.  We can
> normally deduce this by analyzing the socket channel tracepoints, but add
> one for debugging purpose so in a trace log we can see when all channels
> are established.
>
> Add one more for start / resume of incoming migration too.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
>  migration/migration.c  | 3 +++
>  migration/trace-events | 2 ++
>  2 files changed, 5 insertions(+)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index fab7949fe1..3ffc0c2c6a 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -852,6 +852,7 @@ bool migration_incoming_setup(QIOChannel *ioc, uint8_t channel, Error **errp)
>          assert(!mis->from_src_file);
>          mis->from_src_file = f;
>          qemu_file_set_blocking(f, false, &error_abort);
> +        trace_migration_main_channel_received();
>          break;
>  
>      case CH_MULTIFD:
> @@ -918,6 +919,8 @@ static bool postcopy_try_recover(void)
>  
>  void migration_start_incoming(void)
>  {
> +    trace_migration_start_incoming();
> +
>      if (postcopy_try_recover()) {
>          return;
>      }
> diff --git a/migration/trace-events b/migration/trace-events
> index db911fe6f2..68bcf12dc7 100644
> --- a/migration/trace-events
> +++ b/migration/trace-events
> @@ -200,6 +200,8 @@ postcopy_preempt_enabled(bool value) "%d"
>  migration_precopy_complete(void) ""
>  migration_call_notifiers(int type) "type=%d"
>  migration_request_switchover_ack_legacy(const char *requester, unsigned int switchover_ack_pending_num_legacy) "Requester %s, switchover_ack_pending_num_legacy %u"
> +migration_main_channel_received(void) ""
> +migration_start_incoming(void) ""
>  
>  # migration-stats
>  migration_transferred_bytes(uint64_t qemu_file, uint64_t multifd, uint64_t rdma) "qemu_file %" PRIu64 " multifd %" PRIu64 " RDMA %" PRIu64

Reviewed-by: Fabiano Rosas <farosas@suse.de>


  reply	other threads:[~2026-10-14 21:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06 18:20 [PATCH v2 0/7] migration: Fix multifd+postcopy break on qemu-7.2 machine type Peter Xu
2026-10-06 18:20 ` [PATCH v2 1/7] tests/migration-test: Add multifd+postcopy test for preempt recovery Peter Xu
2026-10-14 21:49   ` Fabiano Rosas
2026-10-06 18:20 ` [PATCH v2 2/7] migration: Add two more trace points for incoming channel mgmt Peter Xu
2026-10-14 21:50   ` Fabiano Rosas [this message]
2026-10-06 18:20 ` [PATCH v2 3/7] migration: Fix socket listen backlog Peter Xu
2026-10-06 20:56   ` Daniel P. Berrangé
2026-10-07 19:39     ` Peter Xu
2026-10-14 21:51   ` Fabiano Rosas
2026-10-06 18:20 ` [PATCH v2 4/7] migration: Split migration_channel_process_incoming() Peter Xu
2026-10-15 13:04   ` Fabiano Rosas
2026-10-06 18:20 ` [PATCH v2 5/7] migration: Dump type of channel in set_incoming_channel tracepoint Peter Xu
2026-10-15 13:10   ` Fabiano Rosas
2026-10-06 18:20 ` [PATCH v2 6/7] migration: Fix incoming channel race with multifd and preempt_pre_7_2 Peter Xu
2026-10-15 13:28   ` Fabiano Rosas
2026-10-06 18:20 ` [PATCH v2 7/7] migration: Postpone the outgoing preempt channel for preempt_pre_7_2 Peter Xu
2026-10-15 13:30   ` Fabiano Rosas

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=87ecdslzov.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=akulhall@redhat.com \
    --cc=jmarcin@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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