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;
Date:   Mon, 1 Oct 2018 17:58:57 +0200
From:   Peter Zijlstra <peterz@infradead.org>
To:     Rik van Riel <riel@surriel.com>
Cc:     linux-kernel@vger.kernel.org, kernel-team@fb.com,
        will.deacon@arm.com, songliubraving@fb.com, mingo@kernel.org,
        luto@kernel.org, hpa@zytor.com, npiggin@gmail.com,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Thomas Gleixner <tglx@linutronix.de>, efault@gmx.de
Subject: Re: [PATCH 1/7] x86/mm/tlb: Always use lazy TLB mode
Message-ID: <20181001155857.GK3439@hirez.programming.kicks-ass.net>
References: <20180926035844.1420-1-riel@surriel.com>
 <20180926035844.1420-2-riel@surriel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180926035844.1420-2-riel@surriel.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Sep 25, 2018 at 11:58:38PM -0400, Rik van Riel wrote:
> Now that CPUs in lazy TLB mode no longer receive TLB shootdown IPIs, except
> at page table freeing time, and idle CPUs will no longer get shootdown IPIs
> for things like mprotect and madvise, we can always use lazy TLB mode.

But that's only so at the end of this patch series; either change the
Changelog or the location of this patch?