David Hildenbrand wrote:
> On 11.05.22 01:17, Juan Quintela wrote:
>> We are recalculating ram size continously, when we know that it don't
>> change during migration. Create a field in RAMState to track it.
Hi
> We do have resizable RAM, which triggers ram_mig_ram_block_resized() on
> resizes
On 11.05.22 01:17, Juan Quintela wrote:
> We are recalculating ram size continously, when we know that it don't
> change during migration. Create a field in RAMState to track it.
We do have resizable RAM, which triggers ram_mig_ram_block_resized() on
resizes when changing block->used_length.
ram
We are recalculating ram size continously, when we know that it don't
change during migration. Create a field in RAMState to track it.
Signed-off-by: Juan Quintela
---
migration/ram.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/migration/ram.c b/migration/ram.c
in
