All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Cc: amit.shah@redhat.com
Subject: Re: [Qemu-devel] [PATCH 10/11] migration: create migration event
Date: Wed, 17 Jun 2015 13:45:16 -0600	[thread overview]
Message-ID: <5581CE4C.90700@redhat.com> (raw)
In-Reply-To: <1434505833-11234-11-git-send-email-quintela@redhat.com>

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

On 06/16/2015 07:50 PM, Juan Quintela wrote:
> We have one argument that tells us what event has happened.
> 
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> 
> X3
> 
> Signed-off-by: Juan Quintela <quintela@redhat.com>

Intentional double-S-o-b?

> ---
>  docs/qmp/qmp-events.txt | 14 ++++++++++++++
>  migration/migration.c   |  2 ++
>  qapi/event.json         | 14 ++++++++++++++
>  3 files changed, 30 insertions(+)
> 

> +Data: None.
> +
> + - "status": migration status
> +     See MigrationStatus in ~/qapi-scheme.json for possible values

s/scheme/schema/


> +++ b/qapi/event.json
> @@ -243,6 +243,20 @@
>  { 'event': 'SPICE_MIGRATE_COMPLETED' }
> 
>  ##
> +# @MIGRATION
> +#
> +# Emitted when a migration event happens
> +#
> +# @status: @MigrationStatus describing the current migration status.
> +#          If this field is not returned, no migration process
> +#          has been initiated

Drop this second sentence. 'status' is emitted unconditionally (it is
not marked optional).

With those two changes,
Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


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

  reply	other threads:[~2015-06-17 19:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17  1:50 [Qemu-devel] [PATCH 00/11] Migraiton events + optional sections Juan Quintela
2015-06-17  1:50 ` [Qemu-devel] [PATCH 01/11] runstate: Add runstate store Juan Quintela
2015-06-17 18:39   ` Dr. David Alan Gilbert
2015-06-17  1:50 ` [Qemu-devel] [PATCH 02/11] runstate: migration allows more transitions now Juan Quintela
2015-06-17 18:41   ` Dr. David Alan Gilbert
2015-06-17  1:50 ` [Qemu-devel] [PATCH 03/11] migration: create new section to store global state Juan Quintela
2015-06-17 19:00   ` Dr. David Alan Gilbert
2015-07-01  7:53     ` Juan Quintela
2015-06-17  1:50 ` [Qemu-devel] [PATCH 04/11] global_state: Make section optional Juan Quintela
2015-06-18 11:36   ` Dr. David Alan Gilbert
2015-06-17  1:50 ` [Qemu-devel] [PATCH 05/11] vmstate: Create optional sections Juan Quintela
2015-06-17  1:50 ` [Qemu-devel] [PATCH 06/11] migration: Add configuration section Juan Quintela
2015-06-18 10:27   ` Dr. David Alan Gilbert
2015-06-17  1:50 ` [Qemu-devel] [PATCH 07/11] migration: Use cmpxchg correctly Juan Quintela
2015-06-18 10:33   ` Dr. David Alan Gilbert
2015-06-17  1:50 ` [Qemu-devel] [PATCH 08/11] migration: Use always helper to set state Juan Quintela
2015-06-18 10:46   ` Dr. David Alan Gilbert
2015-07-01  7:33     ` Juan Quintela
2015-06-17  1:50 ` [Qemu-devel] [PATCH 09/11] migration: No need to call trace_migrate_set_state() Juan Quintela
2015-06-18 10:47   ` Dr. David Alan Gilbert
2015-06-17  1:50 ` [Qemu-devel] [PATCH 10/11] migration: create migration event Juan Quintela
2015-06-17 19:45   ` Eric Blake [this message]
2015-07-01  7:22     ` Juan Quintela
2015-06-17  1:50 ` [Qemu-devel] [PATCH 11/11] migration: Add migration events on target side Juan Quintela
2015-06-18 10:53   ` Dr. David Alan Gilbert
2015-06-18 12:19     ` Eric Blake
2015-06-18 12:51       ` Dr. David Alan Gilbert

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=5581CE4C.90700@redhat.com \
    --to=eblake@redhat.com \
    --cc=amit.shah@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 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.