From: Peter Enderborg <peter.enderborg@sony.com>
To: <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Peter Zijlstra <peterz@infradead.org>,
Alexei Starovoitov <ast@kernel.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Michel Lespinasse <walken@google.com>,
Jann Horn <jannh@google.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Christophe Leroy <christophe.leroy@c-s.fr>,
Minchan Kim <minchan@kernel.org>
Subject: [PATCH 0/2] tracing: Add trace for task_exit
Date: Fri, 30 Apr 2021 16:22:21 +0200 [thread overview]
Message-ID: <20210430142223.25500-1-peter.enderborg@sony.com> (raw)
Patch 1 adds a tracepoint for task_exit and use trace strings for that.
the second algin the other (task_newtask and task_rename) to use same
string.
Knowing when and why tasks dies are very useful for varius debugging
aktivites in userspace and we can trace tasks complete life-cycle.
next reply other threads:[~2021-04-30 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 14:22 Peter Enderborg [this message]
2021-04-30 14:22 ` [PATCH 1/2] tracing: Add a trace for task_exit Peter Enderborg
2021-04-30 17:48 ` Eric W. Biederman
2021-05-01 9:29 ` Peter.Enderborg
2021-05-01 13:11 ` Steven Rostedt
2021-05-03 13:50 ` Mathieu Desnoyers
2021-05-03 14:48 ` Peter.Enderborg
2021-05-03 16:30 ` Eric W. Biederman
2021-05-03 18:04 ` Peter.Enderborg
2021-05-03 19:02 ` Eric W. Biederman
2021-05-03 19:43 ` Peter.Enderborg
2021-05-03 20:55 ` Steven Rostedt
2021-05-04 8:00 ` Peter.Enderborg
2021-05-04 13:18 ` Steven Rostedt
2021-04-30 14:22 ` [PATCH 2/2] tracing: Align task.h to use __assing_str for strings Peter Enderborg
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=20210430142223.25500-1-peter.enderborg@sony.com \
--to=peter.enderborg@sony.com \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=christophe.leroy@c-s.fr \
--cc=dave@stgolabs.net \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=walken@google.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