From patchwork Tue Oct 11 06:14:39 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Gavin Shan X-Patchwork-Id: 13003668 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B1B25C433F5 for ; Tue, 11 Oct 2022 06:16:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229459AbiJKGQz (ORCPT ); Tue, 11 Oct 2022 02:16:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40714 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229480AbiJKGQv (ORCPT ); Tue, 11 Oct 2022 02:16:51 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E1EC380484 for ; Mon, 10 Oct 2022 23:16:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1665469008; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=lq6kwFC4jhrgobuRBU2TsyZWnfgf4XHCLQJNWg2urDc=; b=CeK4FetqGMCSKvHiOvrSodo+Lc0bsZ/KR0BotMhGIsJ+fOFoRCR2e0KhZrumCaYGdyJrTX 5ZB7w+z32Dx18QRzJJEZPnT1RbIB5dsBlRTxwm3SBWkNge0MuhcIb9P6f6UID6fibOFMw2 du/n5YwJGJc1EHk+JtfL5RVIdT6zcG0= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-155-iRTsJ3NbP7iJdaVc_NJ4dw-1; Tue, 11 Oct 2022 02:16:45 -0400 X-MC-Unique: iRTsJ3NbP7iJdaVc_NJ4dw-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 42A9A811E81; Tue, 11 Oct 2022 06:16:43 +0000 (UTC) Received: from gshan.redhat.com (vpn2-54-52.bne.redhat.com [10.64.54.52]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C5AAB112D402; Tue, 11 Oct 2022 06:16:36 +0000 (UTC) From: Gavin Shan To: kvmarm@lists.linux.dev Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, peterx@redhat.com, maz@kernel.org, will@kernel.org, catalin.marinas@arm.com, bgardon@google.com, shuah@kernel.org, andrew.jones@linux.dev, dmatlack@google.com, pbonzini@redhat.com, zhenyzha@redhat.com, james.morse@arm.com, suzuki.poulose@arm.com, alexandru.elisei@arm.com, oliver.upton@linux.dev, seanjc@google.com, shan.gavin@gmail.com Subject: [PATCH v6 0/8] KVM: arm64: Enable ring-based dirty memory tracking Date: Tue, 11 Oct 2022 14:14:39 +0800 Message-Id: <20221011061447.131531-1-gshan@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3 Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org This series enables the ring-based dirty memory tracking for ARM64. The feature has been available and enabled on x86 for a while. It is beneficial when the number of dirty pages is small in a checkpointing system or live migration scenario. More details can be found from fb04a1eddb1a ("KVM: X86: Implement ring-based dirty memory tracking"). This series is applied on top of Marc's v2 series [0], fixing dirty-ring ordering issue. This series is going to land on v6.1.rc0 pretty soon. [0] https://lore.kernel.org/kvmarm/20220926145120.27974-1-maz@kernel.org v5: https://lore.kernel.org/all/20221005004154.83502-1-gshan@redhat.com/ v4: https://lore.kernel.org/kvmarm/20220927005439.21130-1-gshan@redhat.com/ v3: https://lore.kernel.org/r/20220922003214.276736-1-gshan@redhat.com v2: https://lore.kernel.org/lkml/YyiV%2Fl7O23aw5aaO@xz-m1.local/T/ v1: https://lore.kernel.org/lkml/20220819005601.198436-1-gshan@redhat.com Testing ======= (1) kvm/selftests/dirty_log_test (2) Live migration by QEMU Changelog ========= v6: * Add CONFIG_HAVE_KVM_DIRTY_RING_WITH_BITMAP, for arm64 to advertise KVM_CAP_DIRTY_RING_WITH_BITMAP in PATCH[v6 3/8] (Oliver/Peter) * Add helper kvm_dirty_ring_exclusive() to check if traditional bitmap-based dirty log tracking is exclusive to dirty-ring in PATCH[v6 3/8] (Peter) * Enable KVM_CAP_DIRTY_RING_WITH_BITMAP in PATCH[v6 5/8] (Gavin) v5: * Drop empty stub kvm_dirty_ring_check_request() (Marc/Peter) * Add PATCH[v5 3/7] to allow using bitmap, indicated by KVM_CAP_DIRTY_LOG_RING_ALLOW_BITMAP (Marc/Peter) v4: * Commit log improvement (Marc) * Add helper kvm_dirty_ring_check_request() (Marc) * Drop ifdef for kvm_cpu_dirty_log_size() (Marc) v3: * Check KVM_REQ_RING_SOFT_RULL inside kvm_request_pending() (Peter) * Move declaration of kvm_cpu_dirty_log_size() (test-robot) v2: * Introduce KVM_REQ_RING_SOFT_FULL (Marc) * Changelog improvement (Marc) * Fix dirty_log_test without knowing host page size (Drew) Gavin Shan (8): KVM: x86: Introduce KVM_REQ_RING_SOFT_FULL KVM: x86: Move declaration of kvm_cpu_dirty_log_size() to kvm_dirty_ring.h KVM: Add support for using dirty ring in conjunction with bitmap KVM: arm64: Enable ring-based dirty memory tracking KVM: selftests: Enable KVM_CAP_DIRTY_LOG_RING_WITH_BITMAP if possible KVM: selftests: Use host page size to map ring buffer in dirty_log_test KVM: selftests: Clear dirty ring states between two modes in dirty_log_test KVM: selftests: Automate choosing dirty ring size in dirty_log_test Documentation/virt/kvm/api.rst | 19 ++++--- arch/arm64/include/uapi/asm/kvm.h | 1 + arch/arm64/kvm/Kconfig | 2 + arch/arm64/kvm/arm.c | 3 ++ arch/x86/include/asm/kvm_host.h | 2 - arch/x86/kvm/x86.c | 15 +++--- include/linux/kvm_dirty_ring.h | 15 +++--- include/linux/kvm_host.h | 2 + include/uapi/linux/kvm.h | 1 + tools/testing/selftests/kvm/dirty_log_test.c | 53 ++++++++++++++------ tools/testing/selftests/kvm/lib/kvm_util.c | 5 +- virt/kvm/Kconfig | 8 +++ virt/kvm/dirty_ring.c | 24 ++++++++- virt/kvm/kvm_main.c | 34 +++++++++---- 14 files changed, 132 insertions(+), 52 deletions(-)