qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: quintela@redhat.com
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, owasserm@redhat.com,
	abali@us.ibm.com, mrhines@us.ibm.com, gokul@us.ibm.com,
	pbonzini@redhat.com, chegu_vinod@hp.com, knoel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v11 14/15] rdma: introduce MIG_STATE_NONE and change MIG_STATE_SETUP state transition
Date: Tue, 25 Jun 2013 09:40:54 -0400	[thread overview]
Message-ID: <51C99DE6.8010606@linux.vnet.ibm.com> (raw)
In-Reply-To: <8761x21pvx.fsf@elfo.elfo>

On 06/25/2013 05:49 AM, Juan Quintela wrote:
> mrhines@linux.vnet.ibm.com wrote:
>> From: "Michael R. Hines" <mrhines@us.ibm.com>
>>
>> As described in the previous patch, until now, the MIG_STATE_SETUP
>> state was not really a 'formal' state. It has been used as a 'zero' state
>> (what we're calling 'NONE' here) and QEMU has been unconditionally transitioning
>> into this state when the QMP migration command was called. Instead we want to
>> introduce MIG_STATE_NONE, which is our starting state in the state machine, and
>> then immediately transition into the MIG_STATE_SETUP state when the QMP migrate
>> command is issued.
>>
>> In order to do this, we must delay the transition into MIG_STATE_ACTIVE until
>> later in the migration_thread(). This is done to be able to timestamp the amount of
>> time spent in the SETUP state for proper accounting to the user during
>> an RDMA migration.
>>
>> Furthermore, the management software, until now, has never been aware of the
>> existence of the SETUP state whatsoever. This must change, because, timing of this
>> state implies that the state actually exists.
>>
>> These two patches cannot be separated because the 'query_migrate' QMP
>> switch statement needs to know how to handle this new state transition.
>>
>> Tested-by: Michael R. Hines <mrhines@us.ibm.com>
>> Signed-off-by: Michael R. Hines <mrhines@us.ibm.com>
>> @@ -316,6 +321,7 @@ static void migrate_fd_cancel(MigrationState *s)
>>   {
>>       DPRINTF("cancelling migration\n");
>>   
>> +    migrate_set_state(s, MIG_STATE_SETUP, MIG_STATE_CANCELLED);
>>       migrate_set_state(s, MIG_STATE_ACTIVE, MIG_STATE_CANCELLED);
>>   }
> This chunk is wrong.
>
> we can call qme_migrate_cancel() at any point,  and it is going to be
> called normally from MIG_STATE_ACTIVE.
>
>
>      migrate_set_satet(s, s->state,  MIG_STATE_CANCELLED)
>
> should do the trick.  Or something like that,  what do you think?
>
> Later,  Juan.
>
>
>

Great idea, thank you.

- Michael

  parent reply	other threads:[~2013-06-25 13:41 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25  1:57 [Qemu-devel] [PATCH v11 00/15] rdma: migration support mrhines
2013-06-25  1:57 ` [Qemu-devel] [PATCH v11 01/15] rdma: add documentation mrhines
2013-06-25 11:54   ` Juan Quintela
2013-06-25  1:57 ` [Qemu-devel] [PATCH v11 02/15] rdma: introduce qemu_update_position() mrhines
2013-06-25  9:24   ` Juan Quintela
2013-06-25  1:57 ` [Qemu-devel] [PATCH v11 03/15] rdma: export yield_until_fd_readable() mrhines
2013-06-25  9:26   ` Juan Quintela
2013-06-25  1:57 ` [Qemu-devel] [PATCH v11 04/15] rdma: export throughput w/ MigrationStats QMP mrhines
2013-06-25  9:27   ` Juan Quintela
2013-06-25 13:36     ` Michael R. Hines
2013-06-25  1:57 ` [Qemu-devel] [PATCH v11 05/15] rdma: introduce qemu_file_mode_is_not_valid() mrhines
2013-06-25  9:28   ` Juan Quintela
2013-06-25  1:57 ` [Qemu-devel] [PATCH v11 06/15] rdma: export qemu_fflush() mrhines
2013-06-25  9:29   ` Juan Quintela
2013-06-25  1:57 ` [Qemu-devel] [PATCH v11 07/15] rdma: introduce ram_handle_compressed() mrhines
2013-06-25  9:30   ` Juan Quintela
2013-06-25  1:57 ` [Qemu-devel] [PATCH v11 08/15] rdma: introduce qemu_ram_foreach_block() mrhines
2013-06-25  9:30   ` Juan Quintela
2013-06-25  1:57 ` [Qemu-devel] [PATCH v11 09/15] rdma: new QEMUFileOps hooks mrhines
2013-06-25 11:51   ` Juan Quintela
2013-06-25 13:38     ` Michael R. Hines
2013-06-25 13:50       ` Paolo Bonzini
2013-06-25  1:58 ` [Qemu-devel] [PATCH v11 10/15] rdma: introduce capability x-rdma-pin-all mrhines
2013-06-25  9:33   ` Juan Quintela
2013-06-25  1:58 ` [Qemu-devel] [PATCH v11 11/15] rdma: core logic mrhines
2013-06-25 12:05   ` Juan Quintela
2013-06-25 13:39     ` Michael R. Hines
2013-06-25 16:31   ` Vasilis Liaskovitis
2013-06-25 16:41     ` Paolo Bonzini
2013-06-25 18:38     ` Michael R. Hines
2013-06-25  1:58 ` [Qemu-devel] [PATCH v11 12/15] rdma: send pc.ram mrhines
2013-06-25  1:58 ` [Qemu-devel] [PATCH v11 13/15] rdma: allow state transitions between other states besides ACTIVE mrhines
2013-06-25  9:40   ` Juan Quintela
2013-06-25  1:58 ` [Qemu-devel] [PATCH v11 14/15] rdma: introduce MIG_STATE_NONE and change MIG_STATE_SETUP state transition mrhines
2013-06-25  9:49   ` Juan Quintela
2013-06-25 10:13     ` Paolo Bonzini
2013-06-25 13:44       ` Michael R. Hines
2013-06-25 13:53         ` Paolo Bonzini
2013-06-25 14:54           ` Michael R. Hines
2013-06-25 14:55             ` Paolo Bonzini
2013-06-25 16:57               ` Michael R. Hines
2013-06-25 20:56               ` Michael R. Hines
2013-06-25 21:06                 ` Paolo Bonzini
2013-06-26  0:31                   ` Michael R. Hines
2013-06-26  6:37                     ` Paolo Bonzini
2013-06-26 12:37                       ` Michael R. Hines
2013-06-26 12:39                         ` Paolo Bonzini
2013-06-26 14:09                           ` Michael R. Hines
2013-06-26 14:57                             ` Paolo Bonzini
2013-06-26 19:25                               ` Michael R. Hines
2013-06-25 14:17         ` Juan Quintela
2013-06-25 17:02           ` Michael R. Hines
2013-06-25 18:48           ` Michael R. Hines
2013-06-25 13:40     ` Michael R. Hines [this message]
2013-06-25  1:58 ` [Qemu-devel] [PATCH v11 15/15] rdma: account for the time spent in MIG_STATE_SETUP through QMP mrhines
2013-06-25  9:50   ` Juan Quintela

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=51C99DE6.8010606@linux.vnet.ibm.com \
    --to=mrhines@linux.vnet.ibm.com \
    --cc=abali@us.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=chegu_vinod@hp.com \
    --cc=gokul@us.ibm.com \
    --cc=knoel@redhat.com \
    --cc=mrhines@us.ibm.com \
    --cc=owasserm@redhat.com \
    --cc=pbonzini@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).