[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250412154751.60224-1-sj@kernel.org>
Date: Sat, 12 Apr 2025 08:47:51 -0700
From: SeongJae Park <sj@...nel.org>
To: "Liam R. Howlett" <Liam.Howlett@...cle.com>
Cc: SeongJae Park <sj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
Vlastimil Babka <vbabka@...e.cz>,
Jann Horn <jannh@...gle.com>
Subject: Re: [PATCH] MAINTAINERS: Add mmap trace events to MEMORY MAPPING
On Sat, 12 Apr 2025 09:17:21 -0400 "Liam R. Howlett" <Liam.Howlett@...cle.com> wrote:
> * SeongJae Park <sj@...nel.org> [250411 13:47]:
[...]
> > > @@ -15571,6 +15571,7 @@ L: linux-mm@...ck.org
> > > S: Maintained
> > > W: http://www.linux-mm.org
> > > T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> > > +F: include/trace/events/mmap.h
> >
> > Should mmap_lock.h also be added here?
>
> Oh, well..
>
> mmap_lock.h (include/trace/events/mmap_lock.h) has to do with
> mm/mmap_lock.c, which also isn't listed here. Both exist for tracing as
> well.
>
> There is also include/linux/mmap_lock.h, which is the locking itself.
> The mmap lock is used more broadly than just these files: mm/pagewalk.c
> and mm/ksm.c, for instance.
>
> So I guess that's a more difficult decision.
Makes perfect sense. Thank you for kindly clarifying this.
Thanks,
SJ
[...]
Powered by blists - more mailing lists