From ee86981bda9ecd40c8daf81b7307b1d2aff68174 Mon Sep 17 00:00:00 2001 From: Peter Maydell Date: Mon, 22 Jan 2018 13:20:14 +0000 Subject: migration: Revert postcopy-blocktime commit set This reverts commits ca6011c migration: add postcopy total blocktime into query-migrate 5f32dc8 migration: add blocktime calculation into migration-test 2f7dae9 migration: postcopy_blocktime documentation 3be98be migration: calculate vCPU blocktime on dst side 01a87f0 migration: add postcopy blocktime ctx into MigrationIncomingState 31bf06a migration: introduce postcopy-blocktime capability as they don't build on ppc32 due to trying to do atomic accesses on types that are larger than the host pointer type. Signed-off-by: Peter Maydell --- docs/devel/migration.rst | 14 -------------- 1 file changed, 14 deletions(-) (limited to 'docs') diff --git a/docs/devel/migration.rst b/docs/devel/migration.rst index 015a9ebdf7..bf97080dac 100644 --- a/docs/devel/migration.rst +++ b/docs/devel/migration.rst @@ -401,20 +401,6 @@ will now cause the transition from precopy to postcopy. It can be issued immediately after migration is started or any time later on. Issuing it after the end of a migration is harmless. -Blocktime is a postcopy live migration metric, intended to show how -long the vCPU was in state of interruptable sleep due to pagefault. -That metric is calculated both for all vCPUs as overlapped value, and -separately for each vCPU. These values are calculated on destination -side. To enable postcopy blocktime calculation, enter following -command on destination monitor: - -``migrate_set_capability postcopy-blocktime on`` - -Postcopy blocktime can be retrieved by query-migrate qmp command. -postcopy-blocktime value of qmp command will show overlapped blocking -time for all vCPU, postcopy-vcpu-blocktime will show list of blocking -time per vCPU. - .. note:: During the postcopy phase, the bandwidth limits set using ``migrate_set_speed`` is ignored (to avoid delaying requested pages that -- cgit v1.2.1