From: Peter Xu <peterx@redhat.com>
To: Prasad Pandit <ppandit@redhat.com>
Cc: qemu-devel@nongnu.org, Fabiano Rosas <farosas@suse.de>,
yong.huang@smartx.com, chen.zhang@intel.com,
Prasad Pandit <pjp@fedoraproject.org>
Subject: Re: [PATCH] migration: correct multifd receive thread name
Date: Wed, 27 Nov 2024 09:31:31 -0500 [thread overview]
Message-ID: <Z0ctQzDaImBmHrh5@x1n> (raw)
In-Reply-To: <20241127111528.167330-1-ppandit@redhat.com>
On Wed, Nov 27, 2024 at 04:45:28PM +0530, Prasad Pandit wrote:
> From: Prasad Pandit <pjp@fedoraproject.org>
>
> Multifd receive threads run on the destination side.
> Correct the thread name marco to indicate the same.
>
> Fixes: e620b1e4770b ("migration: Put thread names together with macros")
> Signed-off-by: Prasad Pandit <pjp@fedoraproject.org>
> ---
> migration/migration.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/migration/migration.h b/migration/migration.h
> index 0956e9274b..3857905c0e 100644
> --- a/migration/migration.h
> +++ b/migration/migration.h
> @@ -37,7 +37,7 @@
> #define MIGRATION_THREAD_SRC_TLS "mig/src/tls"
>
> #define MIGRATION_THREAD_DST_COLO "mig/dst/colo"
> -#define MIGRATION_THREAD_DST_MULTIFD "mig/src/recv_%d"
> +#define MIGRATION_THREAD_DST_MULTIFD "mig/dst/recv_%d"
> #define MIGRATION_THREAD_DST_FAULT "mig/dst/fault"
> #define MIGRATION_THREAD_DST_LISTEN "mig/dst/listen"
> #define MIGRATION_THREAD_DST_PREEMPT "mig/dst/preempt"
> --
> 2.47.0
>
queued for 9.2, thanks.
--
Peter Xu
prev parent reply other threads:[~2024-11-27 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 11:15 [PATCH] migration: correct multifd receive thread name Prasad Pandit
2024-11-27 12:08 ` Fabiano Rosas
2024-11-27 14:31 ` Peter Xu [this message]
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=Z0ctQzDaImBmHrh5@x1n \
--to=peterx@redhat.com \
--cc=chen.zhang@intel.com \
--cc=farosas@suse.de \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yong.huang@smartx.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.