All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: marc.mari.barcelo@gmail.com, pbonzini@redhat.com,
	qemu-block@nongnu.org, qemu-devel@nongnu.org,
	stefanha@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v3 3/9] libqos: Add migration helpers
Date: Mon, 04 May 2015 13:52:14 -0400	[thread overview]
Message-ID: <5547B1CE.1020308@redhat.com> (raw)
In-Reply-To: <20150504120727.GF3676@noname.str.redhat.com>



On 05/04/2015 08:07 AM, Kevin Wolf wrote:
> Am 30.04.2015 um 20:07 hat John Snow geschrieben:
>> libqos.c:
>>      -set_context for addressing which commands go where
>>      -migrate performs the actual migration
>>
>> malloc.c:
>>      - Structure of the allocator is adjusted slightly with
>>        a second-tier malloc to make swapping around the allocators
>>        easy when we "migrate" the lists from the source to the destination.
>>
>> Signed-off-by: John Snow <jsnow@redhat.com>
>> ---
>>   tests/libqos/libqos.c | 84 +++++++++++++++++++++++++++++++++++++++++++++++++++
>>   tests/libqos/libqos.h |  2 ++
>>   tests/libqos/malloc.c | 74 ++++++++++++++++++++++++++++++++++-----------
>>   tests/libqos/malloc.h |  1 +
>>   4 files changed, 144 insertions(+), 17 deletions(-)
>>
>> diff --git a/tests/libqos/libqos.c b/tests/libqos/libqos.c
>> index 7e72078..ac1bae1 100644
>> --- a/tests/libqos/libqos.c
>> +++ b/tests/libqos/libqos.c
>> @@ -1,5 +1,6 @@
>>   #include <stdio.h>
>>   #include <stdlib.h>
>> +#include <string.h>
>>   #include <glib.h>
>>   #include <unistd.h>
>>   #include <fcntl.h>
>> @@ -62,6 +63,89 @@ void qtest_shutdown(QOSState *qs)
>>       g_free(qs);
>>   }
>>
>> +void set_context(QOSState *s)
>> +{
>> +    global_qtest = s->qts;
>> +}
>> +
>> +static QDict *qmp_execute(const char *command)
>> +{
>> +    char *fmt;
>> +    QDict *rsp;
>> +
>> +    fmt = g_strdup_printf("{ 'execute': '%s' }", command);
>> +    rsp = qmp(fmt);
>> +    g_free(fmt);
>> +
>> +    return rsp;
>> +}
>> +
>> +void migrate(QOSState *from, QOSState *to, const char *uri)
>> +{
>> +    const char *st;
>> +    char *s;
>> +    QDict *rsp, *sub;
>> +    bool running;
>> +
>> +    set_context(from);
>> +
>> +    /* Is the machine currently running? */
>> +    rsp = qmp_execute("query-status");
>> +    g_assert(qdict_haskey(rsp, "return"));
>> +    sub = qdict_get_qdict(rsp, "return");
>> +    g_assert(qdict_haskey(sub, "running"));
>> +    running = qdict_get_bool(sub, "running");
>> +    QDECREF(rsp);
>> +
>> +    /* Issue the migrate command. */
>> +    s = g_strdup_printf("{ 'execute': 'migrate',"
>> +                        "'arguments': { 'uri': '%s' } }",
>> +                        uri);
>> +    rsp = qmp(s);
>> +    g_free(s);
>> +    g_assert(qdict_haskey(rsp, "return"));
>> +    QDECREF(rsp);
>> +
>> +    /* Wait for STOP event, but only if we were running: */
>> +    if (running) {
>> +        qmp_eventwait("STOP");
>> +    }
>> +
>> +    /* If we were running, we can wait for an event. */
>> +    if (running) {
>> +        migrate_allocator(from->alloc, to->alloc);
>> +        set_context(to);
>> +        qmp_eventwait("RESUME");
>> +        return;
>> +    }
>> +
>> +    /* Otherwise, we need to wait: poll until migration is completed. */
>> +    while (1) {
>> +        rsp = qmp_execute("query-migrate");
>> +        g_assert(qdict_haskey(rsp, "return"));
>> +        sub = qdict_get_qdict(rsp, "return");
>> +        g_assert(qdict_haskey(sub, "status"));
>> +        st = qdict_get_str(sub, "status");
>> +
>> +        /* "setup", "active", "completed", "failed", "cancelled" */
>> +        if (strcmp(st, "completed") == 0) {
>> +            QDECREF(rsp);
>> +            break;
>> +        }
>> +
>> +        if ((strcmp(st, "setup") == 0) || (strcmp(st, "active") == 0)) {
>> +            QDECREF(rsp);
>> +            continue;
>
> Wouldn't it be nicer to sleep a bit before retrying?
>

I actually figured that all the string and stream manipulation for 
sending and receiving QMP queries was "enough sleep" because of how 
quick a migration without any guest should complete -- in practice this 
loop doesn't ever seem to trigger more than once.

If you still think sleep is necessary, I can add some very small sleep 
in a separate patch, or when I merge the tree. Something like:

g_usleep(5000) /* 5 msec */

>> +        }
>> +
>> +        fprintf(stderr, "Migration did not complete, status: %s\n", st);
>> +        g_assert_not_reached();
>> +    }
>> +
>> +    migrate_allocator(from->alloc, to->alloc);
>> +    set_context(to);
>> +}
>
> Kevin
>

  reply	other threads:[~2015-05-04 17:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 18:07 [Qemu-devel] [PATCH v3 0/9] ahci: enable migration John Snow
2015-04-30 18:07 ` [Qemu-devel] [PATCH v3 1/9] libqos/ahci: Add halted command helpers John Snow
2015-04-30 18:07 ` [Qemu-devel] [PATCH v3 2/9] libqos/ahci: Fix sector set method John Snow
2015-04-30 18:07 ` [Qemu-devel] [PATCH v3 3/9] libqos: Add migration helpers John Snow
2015-05-04 12:07   ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2015-05-04 17:52     ` John Snow [this message]
2015-05-05 11:35       ` Kevin Wolf
2015-05-05 15:50         ` John Snow
2015-04-30 18:07 ` [Qemu-devel] [PATCH v3 4/9] ich9/ahci: Enable Migration John Snow
2015-04-30 18:07 ` [Qemu-devel] [PATCH v3 5/9] qtest/ahci: Add migration test John Snow
2015-04-30 18:07 ` [Qemu-devel] [PATCH v3 6/9] qtest/ahci: add migrate dma test John Snow
2015-04-30 18:07 ` [Qemu-devel] [PATCH v3 7/9] qtest/ahci: add flush migrate test John Snow
2015-04-30 18:07 ` [Qemu-devel] [PATCH v3 8/9] qtest/ahci: add halted dma test John Snow
2015-04-30 18:07 ` [Qemu-devel] [PATCH v3 9/9] qtest/ahci: add migrate " John Snow
2015-05-04 12:29 ` [Qemu-devel] [Qemu-block] [PATCH v3 0/9] ahci: enable migration Kevin Wolf
2015-05-04 15:40   ` John Snow
2015-05-05 22:45 ` [Qemu-devel] " John Snow

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=5547B1CE.1020308@redhat.com \
    --to=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marc.mari.barcelo@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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.