From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mario Smarduch Subject: [PATCH 0/3] migration dirty bitmap support ARMv7 Date: Mon, 14 Apr 2014 18:24:04 -0700 Message-ID: <534C8A34.4090606@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: kvmarm@lists.cs.columbia.edu, christoffer.dall@linaro.org, marc.zyngier@arm.com, =?UTF-8?B?7J207KCV7ISd?= , =?UTF-8?B?7KCV7ISx7KeE?= Return-path: Received: from mailout3.w2.samsung.com ([211.189.100.13]:14024 "EHLO usmailout3.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751054AbaDOBYH (ORCPT ); Mon, 14 Apr 2014 21:24:07 -0400 Received: from uscpsbgex1.samsung.com (u122.gpu85.samsung.co.kr [203.254.195.122]) by usmailout3.samsung.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTP id <0N4100MJMT85UX80@usmailout3.samsung.com> for kvm@vger.kernel.org; Mon, 14 Apr 2014 21:24:05 -0400 (EDT) Sender: kvm-owner@vger.kernel.org List-ID: The patch set supports migration dirty bitmap support implementation for arm-kvm. Spliting of pmd's to pte's as suggested is implemented on demand when migration is started. I tested it on 4-way SMP ARMv7, with SMP guests. 2GB VMs with dirty shared memory segments upto 1.8 GB and relatively fast update rates 16Mb/5mS. Next course of action would be rmap support which scales much better on bigger systems. Although one think that confused me, x86 migrations were sometimes 10 to 15 times slower, I think it must be something wrong with my configuration. Mario Smarduch (3): headers for migration dirtybitmap support initial write protect of VM address space and on dirty log read hooks to interface with QEMU for initial write protect, dirty log read arch/arm/include/asm/kvm_host.h | 9 +++ arch/arm/kvm/arm.c | 62 ++++++++++++++- arch/arm/kvm/mmu.c | 158 ++++++++++++++++++++++++++++++++++++++- 3 files changed, 226 insertions(+), 3 deletions(-) -- 1.7.9.5