From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Ingo Molnar <mingo@elte.hu>,
akpm@linux-foundation.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC patch 02/21] LTTng Kernel Trace Thread Flag ARM fix syscall exit
Date: Sun, 15 Mar 2009 15:35:48 -0400 [thread overview]
Message-ID: <20090315193548.GA10601@Krystal> (raw)
In-Reply-To: <20090315191102.623800671@polymtl.ca>
(sorry, forgot to pick this one from my tree in the original post)
Make sure we re-test the kernel trace thread flag at syscall exit even if we
were not tracing at syscall entry. This fixes syscall exit tracing early in the
trace.
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
---
arch/arm/kernel/entry-common.S | 2 ++
1 file changed, 2 insertions(+)
Index: linux-omap-2.6/arch/arm/kernel/entry-common.S
===================================================================
--- linux-omap-2.6.orig/arch/arm/kernel/entry-common.S 2009-02-21 16:31:10.000000000 +0000
+++ linux-omap-2.6/arch/arm/kernel/entry-common.S 2009-02-21 16:32:18.000000000 +0000
@@ -43,6 +43,8 @@
* Ok, we need to do extra processing, enter the slow path.
*/
fast_work_pending:
+ tst r1, #_TIF_KERNEL_TRACE @ flag can be set asynchronously
+ bne __sys_trace_return
str r0, [sp, #S_R0+S_OFF]! @ returned r0
work_pending:
tst r1, #_TIF_NEED_RESCHED
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2009-03-15 19:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 19:03 [RFC patch 00/21] TIF_KERNEL_TRACE thread flags Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 01/21] LTTng Kernel Trace Thread Flag Alpha Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 02/21] LTTng Kernel Trace Thread Flag ARM Mathieu Desnoyers
2009-03-15 19:35 ` Mathieu Desnoyers [this message]
2009-03-15 19:03 ` [RFC patch 03/21] LTTng Kernel Trace Thread Flag AVR32 Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 04/21] LTTng Kernel Trace Thread Flag Blackfin Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 05/21] LTTng Kernel Trace Thread Flag Cris Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 06/21] LTTng Kernel Trace Thread Flag Frv Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 07/21] LTTng Kernel Trace Thread Flag H8300 Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 08/21] LTTng Kernel Trace Thread Flag ia64 Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 09/21] LTTng Kernel Trace Thread Flag m32r Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 10/21] LTTng Kernel Trace Thread Flag m68k Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 11/21] LTTng Kernel Trace Thread Flag MIPS Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 12/21] LTTng Kernel Trace Thread Flag parisc Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 13/21] LTTng Kernel Trace Thread Flag powerpc Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 14/21] LTTng Kernel Trace Thread Flag s390 Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 15/21] LTTng Kernel Trace Thread Flag SH Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 16/21] LTTng Kernel Trace Thread Flag sparc Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 17/21] LTTng Kernel Trace Thread Flag sparc64 Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 18/21] LTTng Kernel Trace Thread Flag UML Mathieu Desnoyers
2009-03-15 19:03 ` [RFC patch 19/21] LTTng Linux Kernel Trace Thread Flag x86 Mathieu Desnoyers
2009-03-15 19:56 ` Frederic Weisbecker
2009-03-15 20:08 ` Mathieu Desnoyers
2009-03-15 19:04 ` [RFC patch 20/21] LTTng Kernel Trace Thread Flag xtensa Mathieu Desnoyers
2009-03-15 19:04 ` [RFC patch 21/21] LTTng Kernel Trace Thread Flag API Mathieu Desnoyers
2009-03-15 20:03 ` Mathieu Desnoyers
2009-03-15 20:50 ` Frederic Weisbecker
2009-03-15 21:42 ` Mathieu Desnoyers
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=20090315193548.GA10601@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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