Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp7267672rdb; Wed, 3 Jan 2024 09:50:18 -0800 (PST) X-Google-Smtp-Source: AGHT+IHlMORVVcBek3/6etWYJevCmP4xsMwHVg+Q+ly/95bE5k8FfQ6V2aSAYB4eg/EXU+/BtQtW X-Received: by 2002:a50:c313:0:b0:556:c60c:b214 with SMTP id a19-20020a50c313000000b00556c60cb214mr861303edb.20.1704304218364; Wed, 03 Jan 2024 09:50:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1704304218; cv=none; d=google.com; s=arc-20160816; b=GydK6LEDqTf1oYWmEurUeImheUUdBG67OqUDuHkgusjp8KFae5p+gJrXQXlC5ITgNg SI7oAwuUH4j7uldU0QTkMcihKdyZ2qnt6+O5B9LMPTE/eZQj12VJ34I+qFov4RdhtJk5 H+2X+rqIrAgLLspKDwROPU1gixM3UEf92VUVathcJDSLeMd2V/bwB7eymWM0MyZp1CgO 40cb9JOGSCT6BBzqAp4QvSTGhU096LsbhzxOb2DwS9mQVz58dzPpflmaxfcuvar8QYl3 U3mkmn7969Oj4Y8IM932lxdCyuoqPySu49JW5K2+wuzuwmTLxeBaRpqJnaofzqWk6h1o WpvA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version :list-unsubscribe:list-subscribe:list-id:precedence:references :message-id:subject:cc:to:from:date:dkim-signature; bh=/mRn2//JEslwTL2YudTBHyvTAZpl2COitZzMcfSOsiQ=; fh=YxzPfiqeAIB6E5+Bhk3gaNpwZGCtx/yxZqEqIMDGNOk=; b=motfnXjWonIsEFnh9GfqcuZR/LF6pcQNoZBYDX4SIrSmzHCT9WHr8WmuXJavcDBNzg F00l1NTK1fAfdZpWr2k0ncMkqm5ioF56kAibtsTQ4FkYZ0jEFvNDCyIab/2KwRNLW0zr exUZtnMkWQn3IeXgynrBCwFjojrpiJ3xTVlDSFf90uOTiHm1164JttnZzaUN0UODE168 6y1wWnKLBJjwfem+5dOOdd9VAoHzsk80ACBr0AtApJTxsWjq6CuIYPiDpjSzIBr5iyxq UbDFxlKK3aANhMM5eJ5nfz0mjJmgWaqMiEtqohy9GnULFeb2M8+JVpTu1WxRhMsCuh/k 2eBw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=jNPoyeCq; spf=pass (google.com: domain of linux-kernel+bounces-15819-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) smtp.mailfrom="linux-kernel+bounces-15819-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [147.75.80.249]) by mx.google.com with ESMTPS id b6-20020a056402350600b00553fc60e8d6si12809288edd.617.2024.01.03.09.50.18 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 03 Jan 2024 09:50:18 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-15819-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=jNPoyeCq; spf=pass (google.com: domain of linux-kernel+bounces-15819-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) smtp.mailfrom="linux-kernel+bounces-15819-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by am.mirrors.kernel.org (Postfix) with ESMTPS id 0AB401F221F0 for ; Wed, 3 Jan 2024 17:50:18 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 429321C2AD; Wed, 3 Jan 2024 17:50:11 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="jNPoyeCq" X-Original-To: linux-kernel@vger.kernel.org Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 70CF71C296; Wed, 3 Jan 2024 17:50:09 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 148E0C433C8; Wed, 3 Jan 2024 17:50:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1704304208; bh=a1eB5V5dv9FsKtuAgCrEoiM/zZTQE0AOc1G/QrOZMvs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jNPoyeCqDgsu3BE73CiRzBofXmm/w3pz76XB97b/iprlVnMmRWf9yAYU3brWptOXC wx/v9G2JBn/xtRJWz+ZmIoFP/fZ2F+nxqeqUSgB+4PeLfbntRX9gLLbdp1knHXjki1 8QBRTHFkdyIgM1o1z0S+Z+ICo+EiiwXV9DOlV+qNdxTe9oQzjUQuZxSZRhV/SO2QIv AdTisd3vVx2K001275d+QRLb/yghZHtZ8qKpbv0da/tV1s8rEBvtWVDHvvfjAln8v3 MusFr71gFIOgO/A9FAQJpE/UtL+K/3hdUMK4TFO6SDgW3Nnjdb+/PPoLpnkI4OvDhm rtg+LdZPtE5tQ== Date: Wed, 3 Jan 2024 17:50:01 +0000 From: Will Deacon To: Jisheng Zhang Cc: "Aneesh Kumar K . V" , Andrew Morton , Nick Piggin , Peter Zijlstra , Catalin Marinas , Paul Walmsley , Palmer Dabbelt , Albert Ou , Arnd Bergmann , linux-arch@vger.kernel.org, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, Nadav Amit , Andrea Arcangeli , Andy Lutomirski , Dave Hansen , Thomas Gleixner , Yu Zhao , x86@kernel.org Subject: Re: [PATCH 1/2] mm/tlb: fix fullmm semantics Message-ID: <20240103175001.GF5954@willie-the-truck> References: <20231228084642.1765-1-jszhang@kernel.org> <20231228084642.1765-2-jszhang@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231228084642.1765-2-jszhang@kernel.org> User-Agent: Mutt/1.10.1 (2018-07-13) On Thu, Dec 28, 2023 at 04:46:41PM +0800, Jisheng Zhang wrote: > From: Nadav Amit > > fullmm in mmu_gather is supposed to indicate that the mm is torn-down > (e.g., on process exit) and can therefore allow certain optimizations. > However, tlb_finish_mmu() sets fullmm, when in fact it want to say that > the TLB should be fully flushed. > > Change tlb_finish_mmu() to set need_flush_all and check this flag in > tlb_flush_mmu_tlbonly() when deciding whether a flush is needed. > > At the same time, bring the arm64 fullmm on process exit optimization back. > > Signed-off-by: Nadav Amit > Signed-off-by: Jisheng Zhang > Cc: Andrea Arcangeli > Cc: Andrew Morton > Cc: Andy Lutomirski > Cc: Dave Hansen > Cc: Peter Zijlstra > Cc: Thomas Gleixner > Cc: Will Deacon > Cc: Yu Zhao > Cc: Nick Piggin > Cc: x86@kernel.org > --- > arch/arm64/include/asm/tlb.h | 5 ++++- > include/asm-generic/tlb.h | 2 +- > mm/mmu_gather.c | 2 +- > 3 files changed, 6 insertions(+), 3 deletions(-) > > diff --git a/arch/arm64/include/asm/tlb.h b/arch/arm64/include/asm/tlb.h > index 846c563689a8..6164c5f3b78f 100644 > --- a/arch/arm64/include/asm/tlb.h > +++ b/arch/arm64/include/asm/tlb.h > @@ -62,7 +62,10 @@ static inline void tlb_flush(struct mmu_gather *tlb) > * invalidating the walk-cache, since the ASID allocator won't > * reallocate our ASID without invalidating the entire TLB. > */ > - if (tlb->fullmm) { > + if (tlb->fullmm) > + return; > + > + if (tlb->need_flush_all) { > if (!last_level) > flush_tlb_mm(tlb->mm); > return; Why isn't the 'last_level' check sufficient here? In other words, when do we perform a !last_level invalidation with 'fullmm' set outside of teardown? Will