From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Alexey Perevalov <a.perevalov@samsung.com>
Cc: qemu-devel@nongnu.org, v.kuramshin@samsung.com,
ash.billore@samsung.com, f4bug@amsat.org, quintela@redhat.com,
peterx@redhat.com, lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/6] postcopy block time calculation + ppc32 build fix
Date: Thu, 29 Mar 2018 20:18:56 +0100 [thread overview]
Message-ID: <20180329191855.GI2982@work-vm> (raw)
In-Reply-To: <1521742647-25550-1-git-send-email-a.perevalov@samsung.com>
* Alexey Perevalov (a.perevalov@samsung.com) wrote:
> V1-V2
> accidentally appeared __nocheck after rebase
> this patch set also rebased after latest pull request
>
> This patch set includes patches which were reverted by commit
> ee86981bd, due to build problem on 32 powerpc/arm architecture.
> Also it includes patch to fix build
> ([PATCH v4] migration: change blocktime type to uint32_t), but that
> patch was merged into:
> migration: add postcopy blocktime ctx into MigrationIncomingState
> migration: calculate vCPU blocktime on dst side
> migration: add postcopy total blocktime into query-migrate
OK, lets get this in when 2.13 opens.
Thanks!
Dave
>
> based on
> commit c6740fc88ecd8f5cf3cf3185ee112c3eea41caa2
> "hw/rdma: Implementation of PVRDMA device"
>
> 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
>
> docs/devel/migration.rst | 14 +++
> hmp.c | 15 +++
> migration/migration.c | 51 ++++++++-
> migration/migration.h | 13 +++
> migration/postcopy-ram.c | 268 ++++++++++++++++++++++++++++++++++++++++++++++-
> migration/trace-events | 6 +-
> qapi/migration.json | 17 ++-
> tests/migration-test.c | 16 +++
> 8 files changed, 392 insertions(+), 8 deletions(-)
>
> --
> 2.7.4
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-03-29 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180322181739eucas1p2b5f31dc21663881bc244deaedec22712@eucas1p2.samsung.com>
2018-03-22 18:17 ` [Qemu-devel] [PATCH v2 0/6] postcopy block time calculation + ppc32 build fix Alexey Perevalov
[not found] ` <CGME20180322181740eucas1p2a7bde534f74bd8376fc521a4ad1bcfdb@eucas1p2.samsung.com>
2018-03-22 18:17 ` [Qemu-devel] [PATCH v2 1/6] migration: introduce postcopy-blocktime capability Alexey Perevalov
[not found] ` <CGME20180322181740eucas1p13028d8418e837695a91ded89385f8978@eucas1p1.samsung.com>
2018-03-22 18:17 ` [Qemu-devel] [PATCH v2 2/6] migration: add postcopy blocktime ctx into MigrationIncomingState Alexey Perevalov
[not found] ` <CGME20180322181741eucas1p1d80d609a6d0aca10e459563b715b37d6@eucas1p1.samsung.com>
2018-03-22 18:17 ` [Qemu-devel] [PATCH v2 3/6] migration: calculate vCPU blocktime on dst side Alexey Perevalov
[not found] ` <CGME20180322181742eucas1p13b9727b6985dab1ac280f6e07cae9ba6@eucas1p1.samsung.com>
2018-03-22 18:17 ` [Qemu-devel] [PATCH v2 4/6] migration: postcopy_blocktime documentation Alexey Perevalov
[not found] ` <CGME20180322181743eucas1p21654973717f1bfb660fd226f75a206dc@eucas1p2.samsung.com>
2018-03-22 18:17 ` [Qemu-devel] [PATCH v2 5/6] migration: add blocktime calculation into migration-test Alexey Perevalov
[not found] ` <CGME20180322181744eucas1p1a738955967cd8a6cc0330980753b2bad@eucas1p1.samsung.com>
2018-03-22 18:17 ` [Qemu-devel] [PATCH v2 6/6] migration: add postcopy total blocktime into query-migrate Alexey Perevalov
2018-03-29 19:18 ` Dr. David Alan Gilbert [this message]
2018-04-25 16:58 ` [Qemu-devel] [PATCH v2 0/6] postcopy block time calculation + ppc32 build fix Dr. David Alan Gilbert
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=20180329191855.GI2982@work-vm \
--to=dgilbert@redhat.com \
--cc=a.perevalov@samsung.com \
--cc=ash.billore@samsung.com \
--cc=f4bug@amsat.org \
--cc=lvivier@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=v.kuramshin@samsung.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).