From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v3 0/5] KVM: Ring-based dirty memory tracking for performant checkpointing solutions Date: Fri, 3 Feb 2017 23:25:22 -0800 Message-ID: References: <201702031949.v13Jn8eJ032004@dev1.sn.stratus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit To: "Cao, Lei" , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , "kvm@vger.kernel.org" Return-path: Received: from mail-pg0-f68.google.com ([74.125.83.68]:34242 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753803AbdBDHZ0 (ORCPT ); Sat, 4 Feb 2017 02:25:26 -0500 Received: by mail-pg0-f68.google.com with SMTP id v184so3941363pgv.1 for ; Fri, 03 Feb 2017 23:25:26 -0800 (PST) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 03/02/2017 11:58, Cao, Lei wrote: > This patch series adds ring-based dirty memory tracking support for > performant checkpointing solutions. It can also be used by live migration > to improve predictability. Thanks, this looks almost ready. I will include patch 3 already in 4.11. The API also seems easy to use. QEMU can use async_safe_run_on_cpu to stop all CPUs and harvest the dirty pages from the ring buffers, and it can also harvest them in kvm_cpu_exec so that vCPU ring buffers are handled in parallel. I'm sure v4 will be the one! :) Paolo