From: Juan Quintela <quintela@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Eric Blake <eblake@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
Peter Xu <peterx@redhat.com>, Alexey <a.perevalov@samsung.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PULL 00/14] Migration pull request
Date: Tue, 09 Jan 2018 19:28:34 +0100 [thread overview]
Message-ID: <87vagazy25.fsf@secure.laptop> (raw)
In-Reply-To: <CAFEAcA_q9SLzsazfYkRukw+ijOHQTunHqVKqqLhUR_=mqPMPQQ@mail.gmail.com> (Peter Maydell's message of "Tue, 9 Jan 2018 18:24:00 +0000")
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 5 January 2018 at 09:59, Juan Quintela <quintela@redhat.com> wrote:
>> Eric Blake <eblake@redhat.com> wrote:
>>> On 01/03/2018 03:38 AM, Juan Quintela wrote:
>>>> Hi
>>>>
>>>> This are the changes for migration that are already reviewed.
>>>>
>>>> Please, apply.
>>>>
>>>
>>>> Alexey Perevalov (6):
>>>> migration: introduce postcopy-blocktime capability
>>>> migration: add postcopy blocktime ctx into MigrationIncomingState
>>>> migration: calculate vCPU blocktime on dst side
>>>> migration: postcopy_blocktime documentation
>>>> migration: add blocktime calculation into migration-test
>>>> migration: add postcopy total blocktime into query-migrate
>>>
>>> I had unanswered questions about these patches in the v12 series, where
>>> I'm not sure if the interface is still quite right.
>>
>> To be fair, I had alroady integrated the patches before I saw your questions.
>>
>>> We're still early
>>> enough that we could adjust the interface after the fact depending on
>>> how the questions are answered;
>>
>> I think this is the best approach, so far I can see two questions:
>>
>> - do we want to make it conditional? it requires some locking, but I
>> haven't meassured it to see how slow/fast is it.
>>
>> - the other was documentation.
>>
>> I will like Alexey to answer. Depending of how slow it is, I can agree
>> to make it non-optional.
>
> So have you come to a consensus on whether you'd like me to apply
> this pull request or not ?
My understanding is that you should apply it. We will add a
documentation patch later.
Later, Juan.
next prev parent reply other threads:[~2018-01-09 18:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 9:38 [Qemu-devel] [PULL 00/14] Migration pull request Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 01/14] migration: Use proper types in json Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 02/14] migration: print features as on off Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 03/14] migration: free addr in the same function that we created it Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 04/14] docs: Convert migration.txt to rst Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 05/14] migration: free result string Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 06/14] migration: fix analyze-migration.py script with radix table Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 07/14] migration: introduce postcopy-blocktime capability Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 08/14] migration: add postcopy blocktime ctx into MigrationIncomingState Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 09/14] migration: calculate vCPU blocktime on dst side Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 10/14] migration: postcopy_blocktime documentation Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 11/14] migration: add blocktime calculation into migration-test Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 12/14] migration: add postcopy total blocktime into query-migrate Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 13/14] migration: Guard ram_bytes_remaining against early call Juan Quintela
2018-01-03 9:38 ` [Qemu-devel] [PULL 14/14] migration: finalize current_migration object Juan Quintela
2018-01-05 0:30 ` [Qemu-devel] [PULL 00/14] Migration pull request Eric Blake
2018-01-05 9:29 ` Dr. David Alan Gilbert
2018-01-05 9:59 ` Juan Quintela
2018-01-09 18:24 ` Peter Maydell
2018-01-09 18:28 ` Juan Quintela [this message]
2018-01-10 4:58 ` Alexey Perevalov
2018-01-11 11:51 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2017-06-13 9:51 [Qemu-devel] [PULL 00/14] Migration PULL request Juan Quintela
2017-06-13 13:40 ` Peter Maydell
2015-11-19 11:20 [Qemu-devel] [PULL 00/14] Migration pull request Juan Quintela
2015-11-19 13:12 ` Peter Maydell
2015-11-19 13:21 ` Peter Maydell
2015-11-19 14:44 ` Peter Maydell
2015-11-19 15:03 ` Peter Maydell
2015-11-19 15:16 ` Dr. David Alan Gilbert
2015-11-20 8:03 ` Peter Lieven
2015-11-20 9:38 ` Peter Lieven
2015-11-20 11:33 ` Peter Maydell
2015-11-20 13:44 ` Peter Lieven
2015-11-20 13:53 ` Kevin Wolf
2015-11-20 14:00 ` Peter Lieven
2015-11-20 14:15 ` Kevin Wolf
2015-11-19 17:32 ` John Snow
2015-11-19 15:56 ` Peter Maydell
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=87vagazy25.fsf@secure.laptop \
--to=quintela@redhat.com \
--cc=a.perevalov@samsung.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@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.