qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Den Lunev <den@openvz.com>, Paolo Bonzini <pbonzini@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH 1/7] Introduce 'track-writes-ram' migration capability.
Date: Thu, 19 Nov 2020 10:14:24 +0300	[thread overview]
Message-ID: <0bea921c-b38a-703c-9351-597a6344a3f9@virtuozzo.com> (raw)
In-Reply-To: <64a0605b-7a16-1aed-df89-4e605306a241@redhat.com>

On 18.11.2020 17:31, Eric Blake wrote:
> On 11/18/20 5:22 AM, Andrey Gruzdev wrote:
>> Signed-off-by: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
>> ---
>>   migration/migration.c | 96 +++++++++++++++++++++++++++++++++++++++++++
>>   migration/migration.h |  1 +
>>   qapi/migration.json   |  7 +++-
>>   3 files changed, 103 insertions(+), 1 deletion(-)
>>
> 
> Reviewing just the UI:
> 
>> +++ b/qapi/migration.json
>> @@ -442,6 +442,11 @@
>>   # @validate-uuid: Send the UUID of the source to allow the destination
>>   #                 to ensure it is the same. (since 4.2)
>>   #
>> +# @track-writes-ram: If enabled, the migration stream will be a snapshot
>> +#                    of the VM exactly at the point when the migration
>> +#                    procedure starts. The VM RAM is saved with running VM.
>> +#                    (since 5.2)
> 
> This is a new feature, so it is too late for 5.2; this will need to be 6.0.
> 

Yes, agree.

>> +#
>>   # Since: 1.2
>>   ##
>>   { 'enum': 'MigrationCapability',
>> @@ -449,7 +454,7 @@
>>              'compress', 'events', 'postcopy-ram', 'x-colo', 'release-ram',
>>              'block', 'return-path', 'pause-before-switchover', 'multifd',
>>              'dirty-bitmaps', 'postcopy-blocktime', 'late-block-activate',
>> -           'x-ignore-shared', 'validate-uuid' ] }
>> +           'x-ignore-shared', 'validate-uuid', 'track-writes-ram'] }
>>   
>>   ##
>>   # @MigrationCapabilityStatus:
>>
> 

-- 
Andrey Gruzdev, Principal Engineer
Virtuozzo GmbH  +7-903-247-6397
                 virtuzzo.com


  reply	other threads:[~2020-11-19  7:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 11:22 [PATCH 0/7] UFFD write-tracking migration/snapshots Andrey Gruzdev via
2020-11-18 11:22 ` [PATCH 1/7] Introduce 'track-writes-ram' migration capability Andrey Gruzdev via
2020-11-18 14:31   ` Eric Blake
2020-11-19  7:14     ` Andrey Gruzdev [this message]
2020-11-18 11:22 ` [PATCH 2/7] Introduced UFFD-WP low-level interface helpers. Implemented support for the whole RAM block memory protection/un-protection. Higher level ram_write_tracking_start() and ram_write_tracking_stop() to start/stop tracking memory writes on the whole VM memory Andrey Gruzdev via
2020-11-18 11:22 ` [PATCH 3/7] Support UFFD write fault processing in ram_save_iterate() Andrey Gruzdev via
2020-11-18 11:22 ` [PATCH 4/7] Implementation of write-tracking migration thread Andrey Gruzdev via
2020-11-18 11:22 ` [PATCH 5/7] Implementation of vm_start() BH Andrey Gruzdev via
2020-11-18 11:22 ` [PATCH 6/7] The rest of write tracking migration code Andrey Gruzdev via
2020-11-18 11:22 ` [PATCH 7/7] Introduced simple linear scan rate limiting mechanism for write tracking migration Andrey Gruzdev via
2020-11-18 11:39 ` [PATCH 0/7] UFFD write-tracking migration/snapshots no-reply

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=0bea921c-b38a-703c-9351-597a6344a3f9@virtuozzo.com \
    --to=andrey.gruzdev@virtuozzo.com \
    --cc=armbru@redhat.com \
    --cc=den@openvz.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@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).