Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp42176rwd; Wed, 24 May 2023 13:52:45 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7AEjaJnTl6X5jO99yXD0DXGneEaJQcGoh8lwOzq0F0nTzK6grMCmNgyG125B0TMGxHXNYE X-Received: by 2002:a05:6a00:1596:b0:63b:8778:99e4 with SMTP id u22-20020a056a00159600b0063b877899e4mr6221288pfk.2.1684961565248; Wed, 24 May 2023 13:52:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684961565; cv=none; d=google.com; s=arc-20160816; b=GCZ3iSCMRrbm4rR8iMIc6dAQ5ZIjOYvcUdOt7WmcKY31TaAvsmpoqHfuiwpCso0hnp Ozt6u2F0qgBZXgSl1qq7y9TZymGLXAFN7xiTA+yGcRpSvgxI1RNhdqOmQ0ba2g5Y+1/N 7mUHLpyn2IbJANAZXR1TcOThth4UvdhkI32n53IFvaF7Co7VrpNjcP9QVcaSggtchcKo 5Vw3YonadiwSJyPyid8cx/bDnMroHBKNsmVFDoqMyDYHPl2wF2mk4ogzbK0LkGXgVXeF oq9lzJWqpl0xFbPO2JJViIQIqGdqjCtbnxEK+/JXu5f8D40Uv1t5zkaKNbSD1j3k+2jq LINw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=xfybRCqfmly451via0zB+H/Q+AApSu2iaDmN5fGZ/x4=; b=yg8Gy5wKWlQcDlcqrfozDnSvCQuGsAE/gVnjdX2eRPCqf59FiSTTcY34aGX8OLOlJe 9nyTjDDpT/f3Q1GrslkGSJJOhJ1ntX8sf5M3jaMQKjP9+bMunMMWLB7Rv7GTA0RzGQ1A o+rxL5fsJi3LlGeq8X0Fz6jkLfbPcr1XojZinklCVFkiLdekxbI2l3X2zHjA1bW05kNQ mQlnm52WAgajnvxj2QALOP9nW/VccOj7veF1xvqnpozp3RwP57n8OwI3o6L+2sw3fghz kdVTGvaTMEfyfKofcPneTVfStb3ckGvNY2aTAYEryG4K/owxdcaqP3hCSweB8Wz34Bi/ BKlg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b="IgXiGZt/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id n4-20020aa79844000000b0063f1582c50bsi1097226pfq.338.2023.05.24.13.52.30; Wed, 24 May 2023 13:52:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b="IgXiGZt/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236117AbjEXUfC (ORCPT + 99 others); Wed, 24 May 2023 16:35:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41478 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236149AbjEXUev (ORCPT ); Wed, 24 May 2023 16:34:51 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9628E1AC; Wed, 24 May 2023 13:34:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=xfybRCqfmly451via0zB+H/Q+AApSu2iaDmN5fGZ/x4=; b=IgXiGZt/AjIkZyk47M6JmzSETo 5JvYqmTY0S/6CNcf6rOgIUGkx8fCELILrDrVXemYkb5BPYKAn0HI2Y6XB5K+3xzooX2AKsZSw2rzz mh9MKJ/BLQiIqzzeKOeINobvgbeJqtrrw702L1m+480O4PgbeQxZTVHsPTxFOgTQXwjhkEFw9ES3j jYrlmoMd2O6KMc0tFDq7r+mdPcC6sbWD0mdmLQKvSrN/CRbmjwjlImLpNC1DyVuMY2O6L3UPugOJF IUkQyLOL6dwpJlAiac2Dvj+LDhnldubALNgI54EHmr7EPEHVm08LfHTcHZ65apsu3c2zLqTuflfCR 76pcnqHw==; Received: from j130084.upc-j.chello.nl ([24.132.130.84] helo=noisy.programming.kicks-ass.net) by casper.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1q1vAx-00BWOr-Uz; Wed, 24 May 2023 20:33:40 +0000 Received: from hirez.programming.kicks-ass.net (hirez.programming.kicks-ass.net [192.168.1.225]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by noisy.programming.kicks-ass.net (Postfix) with ESMTPS id AD8D830013F; Wed, 24 May 2023 22:33:36 +0200 (CEST) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id D6F5F20A78733; Wed, 24 May 2023 22:33:36 +0200 (CEST) Date: Wed, 24 May 2023 22:33:36 +0200 From: Peter Zijlstra To: Sean Christopherson Cc: Kautuk Consul , Chao Peng , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org, linux-doc@vger.kernel.org, qemu-devel@nongnu.org, linux-kselftest@vger.kernel.org, Paolo Bonzini , Jonathan Corbet , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Thomas Gleixner , Ingo Molnar , Borislav Petkov , x86@kernel.org, "H . Peter Anvin" , Hugh Dickins , Jeff Layton , "J . Bruce Fields" , Andrew Morton , Shuah Khan , Mike Rapoport , Steven Price , "Maciej S . Szmigiero" , Vlastimil Babka , Vishal Annapurve , Yu Zhang , "Kirill A . Shutemov" , luto@kernel.org, jun.nakajima@intel.com, dave.hansen@intel.com, ak@linux.intel.com, david@redhat.com, aarcange@redhat.com, ddutile@redhat.com, dhildenb@redhat.com, Quentin Perret , Michael Roth , mhocko@suse.com, Muchun Song Subject: Re: [PATCH v7 08/14] KVM: Rename mmu_notifier_* Message-ID: <20230524203336.GC3447678@hirez.programming.kicks-ass.net> References: <20220706082016.2603916-1-chao.p.peng@linux.intel.com> <20220706082016.2603916-9-chao.p.peng@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 24, 2023 at 01:16:03PM -0700, Sean Christopherson wrote: > Atomics aren't memory barriers on all architectures, e.g. see the various > definitions of smp_mb__after_atomic(). > > Even if atomic operations did provide barriers, using an atomic would be overkill > and a net negative. On strongly ordered architectures like x86, memory barriers are > just compiler barriers, whereas atomics may be more expensive. Not quite, smp_{r,w}mb() and smp_mb__{before,after}_atomic() are compiler barriers on the TSO archs, but smp_mb() very much isn't. TSO still allows stores to be delayed vs later loads (iow it doesn't pretend to hide the store buffer). > Of course, the only > accesses outside of mmu_lock are reads, so on x86 that "atomic" access is just a > READ_ONCE() load, but that's not the case for all architectures. This is true on *all* archs. atomic_set() and atomic_read() are no more and no less than WRITE_ONCE() / READ_ONCE(). > Anyways, the point is that atomics and memory barriers are different things that > serve different purposes. This is true; esp. on the weakly ordered architectures where atomics do not naturally imply any ordering.