linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Tal Zussman <tz2294@columbia.edu>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Ingo Molnar <mingo@kernel.org>, Rik van Riel <riel@surriel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	x86@kernel.org, Will Deacon <will@kernel.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
	Nick Piggin <npiggin@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH 0/2] x86, mm: minor tlb_flush tracepoint adjustments
Date: Wed, 28 May 2025 11:09:12 +0200	[thread overview]
Message-ID: <ce048e11-f79d-44a6-bacc-46e1ebc34b24@redhat.com> (raw)
In-Reply-To: <20250528-tlb-trace-fix-v1-0-2e94c58f450d@columbia.edu>

On 28.05.25 07:35, Tal Zussman wrote:
> One minor fix and one minor cleanup related to the tlb_flush tracepoint.
> 
> As an aside, include/trace/events/tlb.h isn't covered by MAINTAINERS,
> along with other mm related files under include/trace/events/. Flagging
> this since I see there's a recent effort to overhaul the mm MAINTAINERS
> entries.

Thanks for pointing that out.

It should likely go under "MMU GATHER AND TLB INVALIDATION"

diff --git a/MAINTAINERS b/MAINTAINERS
index 0ecc6063b2b5e..0e88ea5de5b73 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16509,6 +16509,7 @@ L:      linux-mm@kvack.org
  S:     Maintained
  F:     arch/*/include/asm/tlb.h
  F:     include/asm-generic/tlb.h
+F:     include/trace/events/tlb.h
  F:     mm/mmu_gather.c

  MN88472 MEDIA DRIVER


-- 
Cheers,

David / dhildenb



  parent reply	other threads:[~2025-05-28  9:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28  5:35 Tal Zussman
2025-05-28  5:35 ` [PATCH 1/2] x86/tlb/trace: Export the TLB_REMOTE_WRONG_CPU enum Tal Zussman
2025-05-28  9:06   ` David Hildenbrand
2025-06-02 16:52     ` Steven Rostedt
2025-05-28 14:25   ` Rik van Riel
2025-05-28  5:35 ` [PATCH 2/2] mm: Remove tlb_flush_reason::NR_TLB_FLUSH_REASONS Tal Zussman
2025-05-28  9:06   ` David Hildenbrand
2025-05-28 14:26   ` Rik van Riel
2025-05-28  9:09 ` David Hildenbrand [this message]
2025-06-03 22:52   ` [PATCH 0/2] x86, mm: minor tlb_flush tracepoint adjustments Tal Zussman
2025-06-17 20:43 ` Tal Zussman
2025-08-04  9:15   ` Tal Zussman

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=ce048e11-f79d-44a6-bacc-46e1ebc34b24@redhat.com \
    --to=david@redhat.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=npiggin@gmail.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=rostedt@goodmis.org \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=tz2294@columbia.edu \
    --cc=vbabka@suse.cz \
    --cc=will@kernel.org \
    --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