All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 6/6] qapi: Convert migrate
Date: Wed, 15 Feb 2012 14:25:49 +0100	[thread overview]
Message-ID: <87ipj8grdu.fsf@elfo.elfo> (raw)
In-Reply-To: <1328902266-25308-7-git-send-email-lcapitulino@redhat.com> (Luiz Capitulino's message of "Fri, 10 Feb 2012 17:31:06 -0200")

Luiz Capitulino <lcapitulino@redhat.com> wrote:
> The migrate command is one of those commands where HMP and QMP completely
> mix up together. This made the conversion to the QAPI (which separates the
> command into QMP and HMP parts) a bit difficult.
>
> The first important change to be noticed is that this commit completes the
> removal of the Monitor object from migration code, started by the previous
> commit.
>
> Another important and tricky change is about supporting the non-detached
> mode. That's, if the user doesn't pass '-d' the migrate command will lock
> the monitor and will only release it when migration is finished.
>
> To support that in the new HMP command (hmp_migrate()), it was necessary
> to create a timer which runs every second and checks if the migration is
> still active. If it's, the timer callback will re-schedule itself to run
> one second in the future. If the migration has already finished, the
> monitor lock is relased and the user can use it normally.
>
> All these changes should be transparent to the user.

> +static void hmp_migrate_status_cb(void *opaque)
> +{
> +    MigrationStatus *status = opaque;
> +    MigrationInfo *info;
> +
> +    info = qmp_query_migrate(NULL);
> +    if (!info->has_status || strcmp(info->status, "active") == 0) {
> +        qemu_mod_timer(status->timer, qemu_get_clock_ms(rt_clock) +
> 1000);

1 second is one eternity.  I will ask for something smaller (100ms or
200ms range).

> +    qmp_migrate(uri, !!blk, blk, !!inc, inc, false, false, &err);

This is the only user of qmp_migrate, why do we need to pass both
has_blk & blk (and inc and !!inc?)  Both parameters are bool, I am
really confused here.

Later, Juan.

  parent reply	other threads:[~2012-02-15 13:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 19:31 [Qemu-devel] [PATCH 0/6] qapi: Convert migrate Luiz Capitulino
2012-02-10 19:31 ` [Qemu-devel] [PATCH 1/6] QError: Introduce new errors for the migration command Luiz Capitulino
2012-02-15 13:10   ` Juan Quintela
2012-02-10 19:31 ` [Qemu-devel] [PATCH 2/6] monitor: Introduce qemu_get_fd() Luiz Capitulino
2012-02-15 13:11   ` Juan Quintela
2012-02-10 19:31 ` [Qemu-devel] [PATCH 3/6] QDict: Introduce qdict_copy() Luiz Capitulino
2012-02-15 13:10   ` Juan Quintela
2012-02-15 17:01     ` Luiz Capitulino
2012-02-10 19:31 ` [Qemu-devel] [PATCH 4/6] Error: Introduce error_copy() Luiz Capitulino
2012-02-15  9:04   ` Paolo Bonzini
2012-02-15 13:05     ` Luiz Capitulino
2012-02-15 13:16       ` Paolo Bonzini
2012-02-15 13:27   ` Juan Quintela
2012-02-10 19:31 ` [Qemu-devel] [PATCH 5/6] Purge migration of (almost) everything to do with monitors Luiz Capitulino
2012-02-15  9:02   ` Jan Kiszka
2012-02-15 12:53     ` Luiz Capitulino
2012-02-15 13:32       ` Jan Kiszka
2012-02-15 13:15   ` Juan Quintela
2012-02-10 19:31 ` [Qemu-devel] [PATCH 6/6] qapi: Convert migrate Luiz Capitulino
2012-02-15  9:07   ` Wen Congyang
2012-02-15 13:06     ` Luiz Capitulino
2012-02-15 13:25   ` Juan Quintela [this message]
2012-02-15 16:01     ` Michael Roth
2012-02-15 17:13       ` Luiz Capitulino
2012-02-15 13:31   ` Jan Kiszka
2012-02-15 13:44     ` Jan Kiszka
2012-02-15  8:59 ` [Qemu-devel] [PATCH 0/6] " Jan Kiszka
2012-02-15 12:49   ` Luiz Capitulino
2012-02-15 13:34     ` Jan Kiszka
2012-02-15 17:23       ` Luiz Capitulino
2012-02-15 17:39         ` Jan Kiszka
2012-02-15 17:49           ` Luiz Capitulino
2012-02-15 17:56             ` Jan Kiszka

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=87ipj8grdu.fsf@elfo.elfo \
    --to=quintela@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=lcapitulino@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 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.