From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nick Piggin <npiggin@gmail.com>,
Andrew Lutomirski <luto@kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Borislav Petkov <bp@alien8.de>, Will Deacon <will.deacon@arm.com>,
Rik van Riel <riel@surriel.com>, Jann Horn <jannh@google.com>,
Adin Scannell <ascannell@google.com>,
Dave Hansen <dave.hansen@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, David Miller <davem@davemloft.net>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-arch <linux-arch@vger.kernel.org>
Subject: Re: [RFC PATCH 0/2] minor mmu_gather patches
Date: Fri, 24 Aug 2018 10:05:48 +0200 [thread overview]
Message-ID: <20180824080548.GH24124@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+55aFxaiv3SMvFUSEnd_p6nuGttUnv2_O3v_G2zCnnc0pV2pA@mail.gmail.com>
On Thu, Aug 23, 2018 at 12:15:37PM -0700, Linus Torvalds wrote:
> PeterZ - your "mm/tlb, x86/mm: Support invalidating TLB caches for
> RCU_TABLE_FREE" patch looks exactly the same, but it now no longer has
> the split of tlb_flush_mmu_tlbonly(), since with Nick's patch to move
> the call to tlb_table_flush(tlb) into tlb_flush_mmu_free, there's no
> need for the separate double-underscore version.
>
> I hope nothing I did screwed things up. It all looks sane to me.
> Famous last words.
Sorry; I got distracted by building a bunk bed for the kids -- and
somehow these things always take way more time than expected.
Anyway, the code looks good to me. Thanks all!
prev parent reply other threads:[~2018-08-24 8:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 8:47 [RFC PATCH 0/2] minor mmu_gather patches Nicholas Piggin
2018-08-23 8:47 ` [RFC PATCH 1/2] mm: move tlb_table_flush to tlb_flush_mmu_free Nicholas Piggin
2018-08-23 13:40 ` Will Deacon
2018-09-06 20:29 ` Rik van Riel
2018-09-07 13:44 ` Will Deacon
2018-09-07 14:28 ` Rik van Riel
2018-08-23 8:47 ` [RFC PATCH 2/2] mm: mmu_notifier fix for tlb_end_vma Nicholas Piggin
2018-08-23 12:46 ` Catalin Marinas
2018-08-23 13:41 ` Will Deacon
2018-08-24 13:07 ` [RFC PATCH 2/2] mm: mmu_notifier fix for tlb_end_vma (build failures) Guenter Roeck
2018-08-24 13:10 ` Will Deacon
2018-08-24 13:24 ` Guenter Roeck
2018-08-24 13:34 ` Will Deacon
2018-08-24 13:50 ` Will Deacon
2018-08-24 13:54 ` Guenter Roeck
2018-08-24 14:06 ` Guenter Roeck
2018-08-24 14:25 ` Will Deacon
2018-08-24 18:22 ` Guenter Roeck
2018-08-24 23:32 ` Palmer Dabbelt
2018-08-23 19:15 ` [RFC PATCH 0/2] minor mmu_gather patches Linus Torvalds
2018-08-23 19:37 ` Linus Torvalds
2018-08-23 23:27 ` Will Deacon
2018-08-23 23:42 ` Nicholas Piggin
2018-08-23 23:35 ` Nicholas Piggin
2018-08-24 8:05 ` Peter Zijlstra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180824080548.GH24124@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ascannell@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=davem@davemloft.net \
--cc=jannh@google.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=riel@surriel.com \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).