From: Fabiano Rosas <farosas@suse.de>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: "Dr . David Alan Gilbert" <dave@treblig.org>,
"Juraj Marcin" <jmarcin@redhat.com>,
"Prasad Pandit" <ppandit@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Julia Suvorova" <jusual@redhat.com>,
peterx@redhat.com
Subject: Re: [PATCH] migration: Deprecate query-migrationthreads command
Date: Mon, 21 Oct 2024 19:07:55 -0300 [thread overview]
Message-ID: <87y12hcdok.fsf@suse.de> (raw)
In-Reply-To: <20241021215220.982325-1-peterx@redhat.com>
Peter Xu <peterx@redhat.com> writes:
> Per previous discussion [1,2], this patch deprecates query-migrationthreads
> command.
>
> To summarize, the major reason of the deprecation is due to no sensible way
> to consume the API properly:
>
> (1) The reported list of threads are incomplete (ignoring destination
> threads and non-multifd threads).
>
> (2) For CPU pinning, there's no way to properly pin the threads with
> the API if the threads will start running right away after migration
> threads can be queried, so the threads will always run on the default
> cores for a short window.
>
> (3) For VM debugging, one can use "-name $VM,debug-threads=on" instead,
> which will provide proper names for all migration threads.
>
> [1] https://lore.kernel.org/r/20240930195837.825728-1-peterx@redhat.com
> [2] https://lore.kernel.org/r/20241011153417.516715-1-peterx@redhat.com
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
next prev parent reply other threads:[~2024-10-21 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 21:52 [PATCH] migration: Deprecate query-migrationthreads command Peter Xu
2024-10-21 22:07 ` Fabiano Rosas [this message]
2024-10-22 6:18 ` Prasad Pandit
2024-10-22 8:11 ` Daniel P. Berrangé
2024-10-22 8:41 ` Markus Armbruster
2024-10-22 9:21 ` Daniel P. Berrangé
2024-10-22 10:37 ` Markus Armbruster
2024-10-22 10:43 ` Daniel P. Berrangé
2024-10-22 11:40 ` Markus Armbruster
2024-10-22 16:48 ` 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=87y12hcdok.fsf@suse.de \
--to=farosas@suse.de \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dave@treblig.org \
--cc=jmarcin@redhat.com \
--cc=jusual@redhat.com \
--cc=peterx@redhat.com \
--cc=ppandit@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;
as well as URLs for NNTP newsgroup(s).