From: Juan Quintela <quintela@redhat.com>
To: Jiang Jiacheng <jiangjiacheng@huawei.com>
Cc: <qemu-devel@nongnu.org>, <berrange@redhat.com>,
<dgilbert@redhat.com>, <yubihong@huawei.com>,
<xiexiangyou@huawei.com>, <zhengchuan@huawei.com>,
<linyilu@huawei.com>
Subject: Re: [PATCH 2/3] migration: implement query migration threadinfo by name
Date: Mon, 30 Jan 2023 05:27:30 +0100 [thread overview]
Message-ID: <87o7qgode5.fsf@secure.mitica> (raw)
In-Reply-To: <20230120084735.825054-3-jiangjiacheng@huawei.com> (Jiang Jiacheng's message of "Fri, 20 Jan 2023 16:47:34 +0800")
Jiang Jiacheng <jiangjiacheng@huawei.com> wrote:
> Introduce interface query-migrationthreads. The interface is use
> with the migration thread name reported by qemu and returns with
> migration thread name and its pid.
> Introduce threadinfo.c to manage threads with migration.
>
> Signed-off-by: Jiang Jiacheng <jiangjiacheng@huawei.com>
I like this query interface better than the way you expose the thread
name in the 1st place.
But once that we are here, why don't we just "tweak" abit the interface:
> diff --git a/qapi/migration.json b/qapi/migration.json
> index b0cf366ac0..e93c3e560a 100644
> --- a/qapi/migration.json
> +++ b/qapi/migration.json
> @@ -1970,6 +1970,36 @@
> { 'command': 'query-vcpu-dirty-limit',
> 'returns': [ 'DirtyLimitInfo' ] }
>
> +##
> +# @MigrationThreadInfo:
> +#
> +# Information about migrationthreads
> +#
> +# @name: the name of migration thread
> +#
> +# @thread-id: ID of the underlying host thread
> +#
> +# Since: 7.2
> +##
> +{ 'struct': 'MigrationThreadInfo',
> + 'data': {'name': 'str',
> + 'thread-id': 'int'} }
1st, it is an int enough for all architectures? I know that for linux
and friends it is, but not sure about windows and other weird systems.
> +##
> +# @query-migrationthreads:
What about renaming this to:
@query-migrationthread (I removed the last 's')
because it returns the info of a single thread.
> +#
> +# Returns threadInfo about the thread specified by name
> +#
> +# data: migration thread name
> +#
> +# returns: information about the specified thread
> +#
> +# Since: 7.2
> +##
> +{ 'command': 'query-migrationthreads',
> + 'data': { 'name': 'str' },
> + 'returns': 'MigrationThreadInfo' }
> +
> ##
> # @snapshot-save:
> #
And leaves the @query-migrationthreads name for something in the spirit of
> +{ 'command': 'query-migrationthreads',
> + 'returns': ['str'] }
That returns all the migration threads names.
Or perhaps even
> +{ 'command': 'query-migrationthreads',
> + 'returns': ['MigrationThreadInfo'] }
And call it a day?
Later, Juan.
next prev parent reply other threads:[~2023-01-30 4:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 8:47 [RFC PATCH 0/3] migration: support query migration thread information Jiang Jiacheng via
2023-01-20 8:47 ` [PATCH 1/3] migration: report migration thread name to libvirt Jiang Jiacheng via
2023-01-30 4:19 ` Juan Quintela
2023-01-30 12:48 ` Jiang Jiacheng via
2023-01-20 8:47 ` [PATCH 2/3] migration: implement query migration threadinfo by name Jiang Jiacheng via
2023-01-30 4:27 ` Juan Quintela [this message]
2023-01-30 12:48 ` Jiang Jiacheng via
2023-01-30 14:03 ` Juan Quintela
2023-01-31 13:00 ` Jiang Jiacheng via
2023-01-31 16:33 ` Juan Quintela
2023-01-20 8:47 ` [PATCH 3/3] migration: save/delete migration thread info Jiang Jiacheng via
2023-01-30 4:28 ` Juan Quintela
2023-01-30 12:49 ` Jiang Jiacheng via
2023-01-30 14:04 ` Juan Quintela
2023-01-31 13:00 ` Jiang Jiacheng via
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=87o7qgode5.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jiangjiacheng@huawei.com \
--cc=linyilu@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=xiexiangyou@huawei.com \
--cc=yubihong@huawei.com \
--cc=zhengchuan@huawei.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.