From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: LTTng "TIF_KERNEL_TRACE"
Date: Tue, 28 Apr 2009 09:20:37 -0400 [thread overview]
Message-ID: <20090428132037.GA27519@Krystal> (raw)
Hi Ingo,
Looking at the current -tip tree, I notice that the TIF_SYSCALL_FTRACE
flag is only implemented for x86.
I have TIF_KERNEL_TRACE in my lttng tree which applies to all
architectures to do the exact same thing :
lttng-kernel-trace-thread-flag-alpha.patch
lttng-kernel-trace-thread-flag-arm.patch
lttng-kernel-trace-thread-flag-avr32.patch
lttng-kernel-trace-thread-flag-blackfin.patch
lttng-kernel-trace-thread-flag-cris.patch
lttng-kernel-trace-thread-flag-frv.patch
lttng-kernel-trace-thread-flag-h8300.patch
lttng-kernel-trace-thread-flag-ia64.patch
lttng-kernel-trace-thread-flag-m32r.patch
lttng-kernel-trace-thread-flag-m68k.patch
lttng-kernel-trace-thread-flag-mips.patch
lttng-kernel-trace-thread-flag-parisc.patch
lttng-kernel-trace-thread-flag-powerpc.patch
lttng-kernel-trace-thread-flag-s390.patch
lttng-kernel-trace-thread-flag-sh.patch
lttng-kernel-trace-thread-flag-sparc.patch
lttng-kernel-trace-thread-flag-um.patch
lttng-kernel-trace-thread-flag-x86.patch
lttng-kernel-trace-thread-flag-xtensa.patch
lttng-kernel-trace-thread-flag-api.patch
Is there any way we could get this merged ?
One thing I like about the name TIF_KERNEL_TRACE compared to
TIF_SYSCALL_FTRACE is that it gives us a per-thread flag that could
eventually be used for more kernel tracing purposes than just syscalls.
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2009-04-28 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 13:20 Mathieu Desnoyers [this message]
2009-04-28 15:01 ` LTTng "TIF_KERNEL_TRACE" Ingo Molnar
2009-04-28 15:21 ` Mathieu Desnoyers
2009-04-28 15:40 ` Mathieu Desnoyers
2009-04-28 16:33 ` Frederic Weisbecker
2009-04-28 16:37 ` Frédéric Weisbecker
2009-04-28 16:38 ` Mathieu Desnoyers
2009-04-28 16:44 ` Frederic Weisbecker
2009-04-28 16:52 ` Steven Rostedt
2009-04-28 16:43 ` Steven Rostedt
2009-04-28 16:48 ` Frederic Weisbecker
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=20090428132037.GA27519@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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