qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Alexey Perevalov <a.perevalov@samsung.com>, qemu-devel@nongnu.org
Cc: heetae82.ahn@samsung.com, quintela@redhat.com,
	dgilbert@redhat.com, peterx@redhat.com, i.maximets@samsung.com
Subject: Re: [Qemu-devel] [PATCH v12 6/6] migration: add postcopy total blocktime into query-migrate
Date: Tue, 2 Jan 2018 15:26:19 -0600	[thread overview]
Message-ID: <64a69d83-c575-5bd2-66f4-5b88172418a2@redhat.com> (raw)
In-Reply-To: <1509369390-8285-7-git-send-email-a.perevalov@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 2320 bytes --]

On 10/30/2017 08:16 AM, Alexey Perevalov wrote:
> Postcopy total blocktime is available on destination side only.
> But query-migrate was possible only for source. This patch
> adds ability to call query-migrate on destination.
> To be able to see postcopy blocktime, need to request postcopy-blocktime
> capability.

Why not display the stats unconditionally when they are available,
instead of having to set a capability knob to request them?

> 
> The query-migrate command will show following sample result:
> {"return":
>     "postcopy-vcpu-blocktime": [115, 100],
>     "status": "completed",
>     "postcopy-blocktime": 100
> }}
> 
> postcopy_vcpu_blocktime contains list, where the first item is the first
> vCPU in QEMU.
> 
> This patch has a drawback, it combines states of incoming and
> outgoing migration. Ongoing migration state will overwrite incoming
> state. Looks like better to separate query-migrate for incoming and
> outgoing migration or add parameter to indicate type of migration.
> 
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Signed-off-by: Alexey Perevalov <a.perevalov@samsung.com>
> ---

> +++ b/qapi/migration.json
> @@ -156,6 +156,13 @@
>  #              @status is 'failed'. Clients should not attempt to parse the
>  #              error strings. (Since 2.7)
>  #
> +# @postcopy-blocktime: total time when all vCPU were blocked during postcopy
> +#           live migration (Since 2.11)

2.12 now.

Should this mention the capability knob needed to enable this stat (or
else get rid of the capability knob and always expose this when possible)?

> +#
> +# @postcopy-vcpu-blocktime: list of the postcopy blocktime per vCPU (Since 2.11)

Also 2.12.

> +#
> +
> +#
>  # Since: 0.14.0
>  ##
>  { 'struct': 'MigrationInfo',
> @@ -167,7 +174,9 @@
>             '*downtime': 'int',
>             '*setup-time': 'int',
>             '*cpu-throttle-percentage': 'int',
> -           '*error-desc': 'str'} }
> +           '*error-desc': 'str',
> +           '*postcopy-blocktime' : 'int64',
> +           '*postcopy-vcpu-blocktime': ['int64']} }
>  
>  ##
>  # @query-migrate:
> 

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2018-01-02 21:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20171030131646eucas1p14d2fcb39b4916be2960719f68413c082@eucas1p1.samsung.com>
2017-10-30 13:16 ` [Qemu-devel] [PATCH v12 0/6] calculate blocktime for postcopy live migration Alexey Perevalov
     [not found]   ` <CGME20171030131647eucas1p2ea569225550a2250ee75f76b482b7498@eucas1p2.samsung.com>
2017-10-30 13:16     ` [Qemu-devel] [PATCH v12 1/6] migration: introduce postcopy-blocktime capability Alexey Perevalov
2018-01-02 20:49       ` Juan Quintela
2018-01-02 21:20       ` Eric Blake
2018-01-05 12:10         ` Alexey Perevalov
     [not found]   ` <CGME20171030131647eucas1p1b5fb0616e683e78fdca767d267400f50@eucas1p1.samsung.com>
2017-10-30 13:16     ` [Qemu-devel] [PATCH v12 2/6] migration: add postcopy blocktime ctx into MigrationIncomingState Alexey Perevalov
2018-01-02 20:51       ` Juan Quintela
2018-01-02 21:22       ` Eric Blake
2018-01-03  8:25         ` Juan Quintela
     [not found]   ` <CGME20171030131648eucas1p14830b04b73c8eb12d07b752738238b8a@eucas1p1.samsung.com>
2017-10-30 13:16     ` [Qemu-devel] [PATCH v12 3/6] migration: calculate vCPU blocktime on dst side Alexey Perevalov
2017-12-01 18:54       ` Dr. David Alan Gilbert
2018-01-02 20:53       ` Juan Quintela
     [not found]   ` <CGME20171030131649eucas1p1f96847d18071ffdc4ea869438edb2e12@eucas1p1.samsung.com>
2017-10-30 13:16     ` [Qemu-devel] [PATCH v12 4/6] migration: postcopy_blocktime documentation Alexey Perevalov
2018-01-03  8:18       ` Juan Quintela
     [not found]   ` <CGME20171030131650eucas1p11e65153f114fd66677a37751e4e82b2d@eucas1p1.samsung.com>
2017-10-30 13:16     ` [Qemu-devel] [PATCH v12 5/6] migration: add blocktime calculation into migration-test Alexey Perevalov
2018-01-03  8:19       ` Juan Quintela
     [not found]   ` <CGME20171030131650eucas1p183c745b845ded5e02e842582bb44fd7b@eucas1p1.samsung.com>
2017-10-30 13:16     ` [Qemu-devel] [PATCH v12 6/6] migration: add postcopy total blocktime into query-migrate Alexey Perevalov
2018-01-02 21:26       ` Eric Blake [this message]
2018-01-05 12:15         ` Alexey Perevalov
2018-01-05 16:21           ` Eric Blake

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=64a69d83-c575-5bd2-66f4-5b88172418a2@redhat.com \
    --to=eblake@redhat.com \
    --cc=a.perevalov@samsung.com \
    --cc=dgilbert@redhat.com \
    --cc=heetae82.ahn@samsung.com \
    --cc=i.maximets@samsung.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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).