Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp820958ybi; Thu, 30 May 2019 07:16:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqzMti7EGNQa9MemyWmyQXX50Fs8qI6fR5pt2VXJbU9BY3z5EKrmnd/QLae6yGRL4ox2/OBa X-Received: by 2002:a63:4b24:: with SMTP id y36mr3884573pga.36.1559225815472; Thu, 30 May 2019 07:16:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559225815; cv=none; d=google.com; s=arc-20160816; b=ZiInUNSBmnYa6ww1zYgsPOCmODQmdB27kXH0LRBBURnZH63IEKVfDlJPgcpJl6FtS1 oKhQUYZvxgVSlAcgRDoQ07yIL1jzKV0czlWgfVFMnxnChV7rW33uErTZAWGuQbC3RhgF tGPI8ojU/hqZpdSlErPuyVrxHsJ998wsUu0hvPXouYkisKOH6ul/nHzknrJkfrau5clR +dpyhS3Kxw44L4PTOoVlcXD7B3nd0ktjKrtpSA0CBCAjZr7np1ctKBPJjTQMfqBDOLSH Q6S24DP7TxZEuSIrqc34oOpaYwQOgM/CWVhvv3vjFqIQHDfkPhqDHCWj/DurFD5hHepD I2PA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=d6zscDTae9hdY/3BxrAI/3Ni/0wAF+jmCzUyYl+waUs=; b=qJBMXbJScyOzu5AX1Nwl4chqwZf/uLmXKmuPtNCS9/8JACSBimAg/f0Nhs8W/ynn/B n5NbEyDNPCIwnbE+5E86dWp7xmo+j6i6wTM6ZbeYMzM6RKJl/3WrfH0gaS49SuvEP7dX VpzqlGH4JjQuu4QFk2s+90kJ4vN+99mmm+S6SoZen/Jzf4VlWe8J0hEs8iNJLW0aS1sW o9ZokRvTkF5a9lYBmbmJLSKSDCveLhrojQUUHzq35FREC+/Hvm/RhzP6Wo0CnxOZHqtL T8e4ezUbjQ1N3gN+QTFF5AT9L0oQsvkULVtOIMxNIdKHlb03KF25E9ehX2mmy3iD57Ne RFxg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="uZvvF0f/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h9si3138382pjs.74.2019.05.30.07.16.37; Thu, 30 May 2019 07:16:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="uZvvF0f/"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726636AbfE3OPR (ORCPT + 99 others); Thu, 30 May 2019 10:15:17 -0400 Received: from mail.kernel.org ([198.145.29.99]:58752 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725870AbfE3OPR (ORCPT ); Thu, 30 May 2019 10:15:17 -0400 Received: from mail-wm1-f45.google.com (mail-wm1-f45.google.com [209.85.128.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 31D3F25A45 for ; Thu, 30 May 2019 14:15:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559225716; bh=TgiKb0LMDBwyXVpyciZYBGWFy30QWuuM3QhZdETmGI0=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=uZvvF0f/LcJKglvkgh6kWLECMnXX8b/4EAgOWhCACEOnoC+kAAEipNLIxQyXHqUG8 CQMyF0ZlK1PMfnhdK4qKkd50h/vHiIRWDHaaVr4MUgfzjFLgEAng6sDy02j+ChdgZA 8czIPvOWladMb7X1JDN8N+3ORF8KmIKmsu4yNV68= Received: by mail-wm1-f45.google.com with SMTP id g135so894947wme.4 for ; Thu, 30 May 2019 07:15:16 -0700 (PDT) X-Gm-Message-State: APjAAAVnF/RaBG3UF7J0OwzrUp+MgIWex4L0AGF2id0sMGzAifeueZ35 sDF7pX4nAlRhLIvC/7qkQ6Hv/E7uFV8PGkVF3ZRKPQ== X-Received: by 2002:a1c:d10e:: with SMTP id i14mr2546017wmg.161.1559225714741; Thu, 30 May 2019 07:15:14 -0700 (PDT) MIME-Version: 1.0 References: <1559116604-23105-1-git-send-email-zhenzhong.duan@oracle.com> In-Reply-To: <1559116604-23105-1-git-send-email-zhenzhong.duan@oracle.com> From: Andy Lutomirski Date: Thu, 30 May 2019 07:15:02 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] x86/mm/tlb: Do partial TLB flush when possible To: Zhenzhong Duan Cc: LKML , srinivas.eeda@oracle.com, Dave Hansen , Andy Lutomirski , Peter Zijlstra , Thomas Gleixner , Ingo Molnar , Borislav Petkov , X86 ML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 30, 2019 at 12:56 AM Zhenzhong Duan wrote: > > This is a small optimization to stale TLB flush, if there is one new TLB > flush, let it choose to do partial or full flush. or else, the stale > flush take over and do full flush. I think this is invalid because: > > + if (unlikely(f->new_tlb_gen <= local_tlb_gen && > + local_tlb_gen + 1 == mm_tlb_gen)) { > + /* > + * For stale TLB flush request, if there will be one new TLB > + * flush coming, we leave the work to the new IPI as it knows > + * partial or full TLB flush to take, or else we do the full > + * flush. > + */ > + trace_tlb_flush(reason, 0); > + return; We do indeed know that the TLB will get flushed eventually, but we're actually providing a stronger guarantee that the TLB will be adequately flushed by the time we return. Otherwise, after flush_tlb_mm_range(), there will be a window in which the TLB isn't flushed yet.