From mboxrd@z Thu Jan 1 00:00:00 1970 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 mm01.cs.columbia.edu (mm01.cs.columbia.edu [128.59.11.253]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9CBB0C433FE for ; Thu, 29 Sep 2022 14:44:14 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 21AC54B0B9; Thu, 29 Sep 2022 10:44:14 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Authentication-Results: mm01.cs.columbia.edu (amavisd-new); dkim=softfail (fail, message has been altered) header.i=@kernel.org Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zeVIV1Y156fG; Thu, 29 Sep 2022 10:44:13 -0400 (EDT) Received: from mm01.cs.columbia.edu (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 0842543482; Thu, 29 Sep 2022 10:44:13 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 7C7C443399 for ; Thu, 29 Sep 2022 10:44:12 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-vIM1jcddSi for ; Thu, 29 Sep 2022 10:44:10 -0400 (EDT) Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by mm01.cs.columbia.edu (Postfix) with ESMTPS id 117E740FB2 for ; Thu, 29 Sep 2022 10:44:10 -0400 (EDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id B07C7B8246F; Thu, 29 Sep 2022 14:44:08 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 74D11C433C1; Thu, 29 Sep 2022 14:44:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1664462647; bh=Gs9H5OHTr0AT5Xc1QNtEofC7o127qef+wJzsINErOPk=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=deOzK2FtILe0sBjK275mue9L4hd1iXPSKvcW+5SOFWCRBMIWflGcpjDdaOlCUVB35 fHy59rA7tMmmc3xC4vF80htz1rXzypW2HqsT9nhliljKZCDmoAdrjkkzuiGLeXuS9n 0jt/OYUoGpDVpbXXKOZscWJj3P1wEe+lwZDYzKBpTpr/TJi2W+rpnf46FJiRpBMxX2 2EnLe9MCChq4vGQNfzJQSNYteEhqlT34jfUreO7a9kJUvzaT4bXG5HiONbyOlHk5Br jLVSfkI+qrZif6nVzwPVZCkxSIJKQ0SUak+Z3sUgJUuB9FOKmZJjgGrJbJ/sQcjbVc ZIatjAQGtQUZQ== Received: from sofa.misterjones.org ([185.219.108.64] helo=goblin-girl.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1odulh-00DYpR-95; Thu, 29 Sep 2022 15:44:05 +0100 Date: Thu, 29 Sep 2022 15:44:04 +0100 Message-ID: <86edvu6y17.wl-maz@kernel.org> From: Marc Zyngier To: Gavin Shan Subject: Re: [PATCH v4 3/6] KVM: arm64: Enable ring-based dirty memory tracking In-Reply-To: References: <20220927005439.21130-1-gshan@redhat.com> <20220927005439.21130-4-gshan@redhat.com> <86sfkc7mg8.wl-maz@kernel.org> <320005d1-fe88-fd6a-be91-ddb56f1aa80f@redhat.com> <87y1u3hpmp.wl-maz@kernel.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (aarch64-unknown-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") X-SA-Exim-Connect-IP: 185.219.108.64 X-SA-Exim-Rcpt-To: gshan@redhat.com, peterx@redhat.com, kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, catalin.marinas@arm.com, bgardon@google.com, shuah@kernel.org, andrew.jones@linux.dev, will@kernel.org, dmatlack@google.com, pbonzini@redhat.com, zhenyzha@redhat.com, shan.gavin@gmail.com, james.morse@arm.com, suzuki.poulose@arm.com, alexandru.elisei@arm.com, oliver.upton@linux.dev X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Cc: kvm@vger.kernel.org, catalin.marinas@arm.com, andrew.jones@linux.dev, will@kernel.org, shan.gavin@gmail.com, bgardon@google.com, dmatlack@google.com, pbonzini@redhat.com, zhenyzha@redhat.com, shuah@kernel.org, kvmarm@lists.cs.columbia.edu X-BeenThere: kvmarm@lists.cs.columbia.edu X-Mailman-Version: 2.1.14 Precedence: list List-Id: Where KVM/ARM decisions are made List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu On Thu, 29 Sep 2022 12:31:34 +0100, Gavin Shan wrote: > > I've had the following PATCH[v5 3/7] to reuse bitmap for these particular > cases. KVM_GET_DIRTY_LOG and KVM_CLEAR_DIRTY_LOG ioctls are used to visit > the bitmap. The new capability is advertised by KVM_CAP_DIRTY_LOG_RING_BITMAP. > Note those two ioctls are disabled when dirty-ring is enabled, we need to > enable them accordingly. > > PATCH[v5 3/7] KVM: x86: Use bitmap in ring-based dirty page tracking > > I would like to post v5 after someone reviews or acks kvm/selftests part > of this series. Feel free to post the series. This is too late for 6.1 anyway (I'll probably send the PR to Paolo tomorrow), so this gives us plenty of time to sort this out. M. -- Without deviation from the norm, progress is not possible. _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm