From: Karim Yaghmour via lttng-dev <lttng-dev@lists.lttng.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: wenyang.linux@foxmail.com, Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org,
lttng-dev <lttng-dev@lists.lttng.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mel Gorman <mgorman@techsingularity.net>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [lttng-dev] [PATCH] coredump debugging: add a tracepoint to report the coredumping
Date: Fri, 23 Feb 2024 12:12:47 -0500 [thread overview]
Message-ID: <ee3dbbfa-2ef1-4481-b67b-80dcd3c7010d@opersys.com> (raw)
In-Reply-To: <c9427e40-10b1-49eb-9baa-dde1364e8fe5@efficios.com>
On 2/23/24 11:54, Mathieu Desnoyers wrote:
...
> So this sched_process_exit placement was actually decided
> by Karim Yaghmour back in the LTT days (2001). I don't think
> he will mind us moving it around some 23 years later. ;)
Gee ... the shadows are longer than I thought :)
It's all yours. You guys have been doing a fantastic job and I'm happy
to be on the consumer side of it all these days :D
Cheers,
--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2024-02-23 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_5CD40341EC9384E9B7CC127EA5CF2655B408@qq.com>
[not found] ` <20240217104924.GB10393@redhat.com>
[not found] ` <20240219112926.77ac16f8@gandalf.local.home>
[not found] ` <20240219170038.GA710@redhat.com>
[not found] ` <20240219122825.31579a1e@gandalf.local.home>
[not found] ` <776b842b-b19f-44bf-bc34-ac756fce7466@efficios.com>
[not found] ` <20240223092630.49b9d367@gandalf.local.home>
2024-02-23 16:54 ` [lttng-dev] [PATCH] coredump debugging: add a tracepoint to report the coredumping Mathieu Desnoyers via lttng-dev
2024-02-23 17:03 ` Steven Rostedt via lttng-dev
2024-02-23 17:12 ` Karim Yaghmour via lttng-dev [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=ee3dbbfa-2ef1-4481-b67b-80dcd3c7010d@opersys.com \
--to=lttng-dev@lists.lttng.org \
--cc=karim.yaghmour@opersys.com \
--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=rostedt@goodmis.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).