Blame SOURCES/kvm-migration-calculate-expected_downtime-with-ram_bytes.patch

ae23c9
From 1c9e86aac83e91498772885f5223e212337a3ff9 Mon Sep 17 00:00:00 2001
ae23c9
From: Laurent Vivier <lvivier@redhat.com>
ae23c9
Date: Thu, 21 Jun 2018 09:45:26 +0200
ae23c9
Subject: [PATCH 075/268] migration: calculate expected_downtime with
ae23c9
 ram_bytes_remaining()
ae23c9
ae23c9
RH-Author: Laurent Vivier <lvivier@redhat.com>
ae23c9
Message-id: <20180621094526.5714-1-lvivier@redhat.com>
ae23c9
Patchwork-id: 80931
ae23c9
O-Subject: [RHEL-7.6 qemu-kvm-rhev PATCH] migration: calculate expected_downtime with ram_bytes_remaining()
ae23c9
Bugzilla: 1564576
ae23c9
RH-Acked-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
ae23c9
RH-Acked-by: Thomas Huth <thuth@redhat.com>
ae23c9
RH-Acked-by: David Gibson <dgibson@redhat.com>
ae23c9
ae23c9
From: Balamuruhan S <bala24@linux.vnet.ibm.com>
ae23c9
ae23c9
expected_downtime value is not accurate with dirty_pages_rate * page_size,
ae23c9
using ram_bytes_remaining() would yeild it resonable.
ae23c9
ae23c9
consider to read the remaining ram just after having updated the dirty
ae23c9
pages count later migration_bitmap_sync_range() in migration_bitmap_sync()
ae23c9
and reuse the `remaining` field in ram_counters to hold ram_bytes_remaining()
ae23c9
for calculating expected_downtime.
ae23c9
ae23c9
Reported-by: Michael Roth <mdroth@linux.vnet.ibm.com>
ae23c9
Signed-off-by: Balamuruhan S <bala24@linux.vnet.ibm.com>
ae23c9
Signed-off-by: Laurent Vivier <lvivier@redhat.com>
ae23c9
Message-Id: <20180612085009.17594-2-bala24@linux.vnet.ibm.com>
ae23c9
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
ae23c9
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
ae23c9
(cherry picked from commit 650af8907bd567db914b7ce3a7e9df4c323f4619)
ae23c9
Signed-off-by: Laurent Vivier <lvivier@redhat.com>
ae23c9
Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
ae23c9
---
ae23c9
 migration/migration.c | 3 +--
ae23c9
 migration/ram.c       | 1 +
ae23c9
 2 files changed, 2 insertions(+), 2 deletions(-)
ae23c9
ae23c9
diff --git a/migration/migration.c b/migration/migration.c
ae23c9
index ef4bb42..43d8a64 100644
ae23c9
--- a/migration/migration.c
ae23c9
+++ b/migration/migration.c
ae23c9
@@ -2239,8 +2239,7 @@ static void migration_update_counters(MigrationState *s,
ae23c9
      * recalculate. 10000 is a small enough number for our purposes
ae23c9
      */
ae23c9
     if (ram_counters.dirty_pages_rate && transferred > 10000) {
ae23c9
-        s->expected_downtime = ram_counters.dirty_pages_rate *
ae23c9
-            qemu_target_page_size() / bandwidth;
ae23c9
+        s->expected_downtime = ram_counters.remaining / bandwidth;
ae23c9
     }
ae23c9
 
ae23c9
     qemu_file_reset_rate_limit(s->to_dst_file);
ae23c9
diff --git a/migration/ram.c b/migration/ram.c
ae23c9
index 0e90efa..00c06b5 100644
ae23c9
--- a/migration/ram.c
ae23c9
+++ b/migration/ram.c
ae23c9
@@ -852,6 +852,7 @@ static void migration_bitmap_sync(RAMState *rs)
ae23c9
     RAMBLOCK_FOREACH(block) {
ae23c9
         migration_bitmap_sync_range(rs, block, 0, block->used_length);
ae23c9
     }
ae23c9
+    ram_counters.remaining = ram_bytes_remaining();
ae23c9
     rcu_read_unlock();
ae23c9
     qemu_mutex_unlock(&rs->bitmap_mutex);
ae23c9
 
ae23c9
-- 
ae23c9
1.8.3.1
ae23c9