From: Steven Rostedt <rostedt@goodmis.org>
To: Wen Yang <wenyang.linux@foxmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mel Gorman <mgorman@techsingularity.net>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] coredump debugging: add a tracepoint to report the coredumping
Date: Wed, 21 Feb 2024 12:54:20 -0500 [thread overview]
Message-ID: <20240221125420.3430eae5@gandalf.local.home> (raw)
In-Reply-To: <tencent_842730EBF8FD3CA3564D50CF04654D52A40A@qq.com>
On Thu, 22 Feb 2024 00:00:55 +0800
Wen Yang <wenyang.linux@foxmail.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
next prev parent reply other threads:[~2024-02-21 17:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 18:59 wenyang.linux
2024-02-17 10:49 ` Oleg Nesterov
2024-02-18 15:16 ` Wen Yang
2024-02-18 17:52 ` Oleg Nesterov
2024-02-19 16:29 ` Steven Rostedt
2024-02-19 17:00 ` Oleg Nesterov
2024-02-19 17:28 ` Steven Rostedt
2024-02-19 18:01 ` Mathieu Desnoyers
2024-02-20 15:08 ` Steven Rostedt
2024-02-23 14:26 ` Steven Rostedt
2024-02-23 16:54 ` Mathieu Desnoyers
2024-02-23 17:03 ` Steven Rostedt
2024-02-23 17:12 ` Karim Yaghmour
2024-02-21 16:00 ` Wen Yang
2024-02-21 17:54 ` Steven Rostedt [this message]
2024-02-21 15:45 ` Wen Yang
2024-02-21 17:48 ` Steven Rostedt
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=20240221125420.3430eae5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@techsingularity.net \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=wenyang.linux@foxmail.com \
/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
all inboxes | Powered by JetHome®