qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Perevalov <a.perevalov@samsung.com>
To: qemu-devel@nongnu.org, dgilbert@redhat.com
Cc: Alexey Perevalov <a.perevalov@samsung.com>,
	v.kuramshin@samsung.com, ash.billore@samsung.com,
	f4bug@amsat.org, quintela@redhat.com, peterx@redhat.com,
	lvivier@redhat.com
Subject: [Qemu-devel] [PATCH v1 0/6] postcopy block time calculation + ppc32 build fix
Date: Tue, 13 Mar 2018 17:53:38 +0300	[thread overview]
Message-ID: <1520952824-3172-1-git-send-email-a.perevalov@samsung.com> (raw)
In-Reply-To: CGME20180313145356eucas1p24b7192c7bc7ecbfd5687c59ae0e649ab@eucas1p2.samsung.com

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

based on
commit 12c06d6f967a63515399b9e1f6a40f5ce871a8b7
Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging


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 | 266 ++++++++++++++++++++++++++++++++++++++++++++++-
 migration/trace-events   |   6 +-
 qapi/migration.json      |  17 ++-
 tests/migration-test.c   |  16 +++
 8 files changed, 390 insertions(+), 8 deletions(-)

-- 
2.7.4

       reply	other threads:[~2018-03-13 14:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180313145356eucas1p24b7192c7bc7ecbfd5687c59ae0e649ab@eucas1p2.samsung.com>
2018-03-13 14:53 ` Alexey Perevalov [this message]
2018-03-13 14:53   ` [Qemu-devel] [PATCH v1 1/6] migration: introduce postcopy-blocktime capability Alexey Perevalov
2018-03-13 14:53   ` [Qemu-devel] [PATCH v1 2/6] migration: add postcopy blocktime ctx into MigrationIncomingState Alexey Perevalov
2018-03-13 14:53   ` [Qemu-devel] [PATCH v1 3/6] migration: calculate vCPU blocktime on dst side Alexey Perevalov
2018-03-21 12:24     ` Dr. David Alan Gilbert
2018-03-13 14:53   ` [Qemu-devel] [PATCH v1 4/6] migration: postcopy_blocktime documentation Alexey Perevalov
2018-03-13 14:53   ` [Qemu-devel] [PATCH v1 5/6] migration: add blocktime calculation into migration-test Alexey Perevalov
2018-03-13 14:53   ` [Qemu-devel] [PATCH v1 6/6] migration: add postcopy total blocktime into query-migrate Alexey Perevalov

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=1520952824-3172-1-git-send-email-a.perevalov@samsung.com \
    --to=a.perevalov@samsung.com \
    --cc=ash.billore@samsung.com \
    --cc=dgilbert@redhat.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).