[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240221125420.3430eae5@gandalf.local.home>
Date: Wed, 21 Feb 2024 12:54:20 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Wen Yang <wenyang.linux@...mail.com>
Cc: Oleg Nesterov <oleg@...hat.com>, Masami Hiramatsu <mhiramat@...nel.org>,
Ingo Molnar <mingo@...nel.org>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Mel Gorman <mgorman@...hsingularity.net>,
Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] coredump debugging: add a tracepoint to report the
coredumping
On Thu, 22 Feb 2024 00:00:55 +0800
Wen Yang <wenyang.linux@...mail.com> wrote:
> > Honestly, if anything, it should probably be moved down right next to
> > () (I never understood why needed its own hooks
> > and not just use tracepoints).
> >
>
> Perhaps it's just because perf appeared earlier, and it doesn't rely on
> TRACEPOINTS.
tracepoints existed in 2008 and perf was added in 2009, so time frame was
not a factor.
> It is indeed reasonable to replace perf_event_exit_task() with
> TRACEPOINT, and we are willing to try to modify it. It will require some
> work and time.
I think that would be worth while, but I guess Peter will need to approve that.
-- Steve
Powered by blists - more mailing lists