From: Markus Armbruster <armbru@redhat.com>
To: Andrey Gruzdev via <qemu-devel@nongnu.org>
Cc: Juan Quintela <quintela@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Peter Xu <peterx@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>,
Den Lunev <den@openvz.org>,
Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
Subject: Re: [PATCH v9 1/5] migration: introduce 'background-snapshot' migration capability
Date: Thu, 17 Dec 2020 17:29:26 +0100 [thread overview]
Message-ID: <87a6ucgzvd.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20201217144540.365903-2-andrey.gruzdev@virtuozzo.com> (Andrey Gruzdev via's message of "Thu, 17 Dec 2020 17:45:36 +0300")
Andrey Gruzdev via <qemu-devel@nongnu.org> writes:
> Add new capability to 'qapi/migration.json' schema.
> Update migrate_caps_check() to validate enabled capability set
> against introduced one. Perform checks for required kernel features
> and compatibility with guest memory backends.
>
> Signed-off-by: Andrey Gruzdev <andrey.gruzdev@virtuozzo.com>
> Reviewed-by: Peter Xu <peterx@redhat.com>
You dropped the
Acked-by: Markus Armbruster <armbru@redhat.com>
I gave for v6. Intentional?
next prev parent reply other threads:[~2020-12-17 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 14:45 [PATCH v9 0/5] UFFD write-tracking migration/snapshots Andrey Gruzdev via
2020-12-17 14:45 ` [PATCH v9 1/5] migration: introduce 'background-snapshot' migration capability Andrey Gruzdev via
2020-12-17 16:29 ` Markus Armbruster [this message]
2020-12-17 16:40 ` Andrey Gruzdev
2020-12-17 14:45 ` [PATCH v9 2/5] migration: introduce UFFD-WP low-level interface helpers Andrey Gruzdev via
2020-12-17 14:45 ` [PATCH v9 3/5] migration: support UFFD write fault processing in ram_save_iterate() Andrey Gruzdev via
2020-12-17 14:45 ` [PATCH v9 4/5] migration: implementation of background snapshot thread Andrey Gruzdev via
2020-12-17 14:45 ` [PATCH v9 5/5] migration: introduce 'userfaultfd-wrlat.py' script Andrey Gruzdev via
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=87a6ucgzvd.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=andrey.gruzdev@virtuozzo.com \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@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 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.