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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3ADE7C77B61 for ; Fri, 21 Apr 2023 17:11:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Subject:Cc:To:From:Message-ID:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=oCSzCiCzJU8HQhFJVJTd5wPWSoyjaKx3EoLrRxsHeBM=; b=O9P0ITg9fd5Xsd ZA5fuQhXc0JjUM6DTMjuFKzazwdKE0xiLZHO4+UCFvha9HiZUJ7W1lEifkT3rFB51EfUCs3eNCAdY cbnecPW+o0FnJVNOqC4XWX1guVjsqTf0nQ2uXrRNiMpEqxzPHLQhxWnHrjaDQcYvhh2fMiXgbbhbh a6Ku3Mp1l3+h1dUkGfFVcxJF7zS9Pt1FcwfYEoWSxjnKDa2YocEPtfrzt6WK5oixly9dowwgZdFXz M87AncZQmnToWDckE82XEe580TBRwD/G3J8hAlandLVs48N8Yz8xzy2IFSSxXURWJvKfCMfPIQL5I /5Xh519IT5s3WfheH3dw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1ppuHt-00BSwe-1g; Fri, 21 Apr 2023 17:11:09 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1ppuHm-00BSvs-30; Fri, 21 Apr 2023 17:11:07 +0000 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 dfw.source.kernel.org (Postfix) with ESMTPS id 4C15563CBF; Fri, 21 Apr 2023 17:11:01 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B12ECC433D2; Fri, 21 Apr 2023 17:11:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1682097060; bh=DnRJVkdO+iXXcujqYX0KJiluJwWD+2pWlYT4caOjV0E=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=EHqT+C8njFjfHsi70rZiFdTrbu/ie2fbzv5GWFi7pafMAdvhkg+xjmdkME5V+TP5H vcLBHMLLGFbsS6Bh5vypOpKExqOA8wsRzF41qmZ19WzWKshlk3u9i0D0aXorNQzjsL nQpYWA+mm/4JtT8Uwm4DBOpUtNdlt85q/uiLWvjEUOn2ZnHqCgjzx1pGUZyWRwl9U3 I41Jwu+sshMCbAC8Y0Ew+K9z6kUOnYFRIA8TNf11u2KxRLFc8FeFiRoyQxIli0As/N m14zF/WcXp/SNioGllvt5vra6edJysaPm4tYR2VfzMlV49j4IaFjTG0hvQMliIapd3 qihad4ZVYUIAA== 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 1ppuHi-00AFeg-8D; Fri, 21 Apr 2023 18:10:58 +0100 Date: Fri, 21 Apr 2023 18:10:57 +0100 Message-ID: <86pm7xjh3y.wl-maz@kernel.org> From: Marc Zyngier To: Vipin Sharma Cc: oliver.upton@linux.dev, james.morse@arm.com, suzuki.poulose@arm.com, yuzenghui@huawei.com, catalin.marinas@arm.com, will@kernel.org, chenhuacai@kernel.org, aleksandar.qemu.devel@gmail.com, tsbogend@alpha.franken.de, anup@brainfault.org, atishp@atishpatra.org, paul.walmsley@sifive.com, palmer@dabbelt.com, aou@eecs.berkeley.edu, seanjc@google.com, pbonzini@redhat.com, dmatlack@google.com, ricarkol@google.com, linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, linux-mips@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kselftest@vger.kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 9/9] KVM: arm64: Run clear-dirty-log under MMU read lock In-Reply-To: <20230421165305.804301-10-vipinsh@google.com> References: <20230421165305.804301-1-vipinsh@google.com> <20230421165305.804301-10-vipinsh@google.com> 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/28.2 (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: vipinsh@google.com, oliver.upton@linux.dev, james.morse@arm.com, suzuki.poulose@arm.com, yuzenghui@huawei.com, catalin.marinas@arm.com, will@kernel.org, chenhuacai@kernel.org, aleksandar.qemu.devel@gmail.com, tsbogend@alpha.franken.de, anup@brainfault.org, atishp@atishpatra.org, paul.walmsley@sifive.com, palmer@dabbelt.com, aou@eecs.berkeley.edu, seanjc@google.com, pbonzini@redhat.com, dmatlack@google.com, ricarkol@google.com, linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, linux-mips@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kselftest@vger.kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230421_101103_134536_8C55CAB7 X-CRM114-Status: GOOD ( 13.87 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org On Fri, 21 Apr 2023 17:53:05 +0100, Vipin Sharma wrote: > > Take MMU read lock for write protecting PTEs and use shared page table > walker for clearing dirty logs. > > Clearing dirty logs are currently performed under MMU write locks. This > means vCPUs write protection fault, which also take MMU read lock, will > be blocked during this operation. This causes guest degradation and > especially noticeable on VMs with lot of vCPUs. > > Taking MMU read lock will allow vCPUs to execute parallelly and reduces > the impact on vCPUs performance. Sure. Taking no lock whatsoever would be even better. What I don't see is the detailed explanation that gives me the warm feeling that this is safe and correct. Such an explanation is the minimum condition for me to even read the patch. Thanks, M. -- Without deviation from the norm, progress is not possible. _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv