From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] ARM: ensure sched_clock() and children are notrace
Date: Fri, 19 Nov 2010 21:39:29 +0530 [thread overview]
Message-ID: <20101119160849.GA21870@debian> (raw)
In-Reply-To: <AANLkTik9Wv2p9-=X3roJut3A3KLD1D7UWOB795edjHAX@mail.gmail.com>
> On Sat, Nov 6, 2010 at 11:55 PM, Rabin Vincent <rabin@rab.in> wrote:
> > Include sched.h in the files implementing sched_clock() and ensure that
> > any functions called from sched_clock() have the notrace annotation.
On Sat, Nov 13, 2010 at 12:14:51AM +0530, Rabin Vincent wrote:
> CC'd some mach maintainers. I can split this up if needed,
> since these bits can be applied independently from the rest
> of the patches in the series.
I've split it up anyway, since tegra and nomadik have since fixed it
themselves while reworking their sched_clock() implementations (and
there are probably others who need to do this), and I missed a couple of
functions in omap and u300 in the first patch.
WARNING: multiple messages have this Message-ID (diff)
From: Rabin Vincent <rabin@rab.in>
To: linux-arm-kernel@lists.infradead.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Tim Bird <tim.bird@am.sony.com>,
linux-kernel@vger.kernel.org, Colin Cross <ccross@android.com>,
Erik Gilling <konkers@android.com>,
Olof Johansson <olof@lixom.net>,
Linus Walleij <linus.walleij@stericsson.com>,
Mikael Pettersson <mikpe@it.uu.se>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 1/6] ARM: ensure sched_clock() and children are notrace
Date: Fri, 19 Nov 2010 21:39:29 +0530 [thread overview]
Message-ID: <20101119160849.GA21870@debian> (raw)
In-Reply-To: <AANLkTik9Wv2p9-=X3roJut3A3KLD1D7UWOB795edjHAX@mail.gmail.com>
> On Sat, Nov 6, 2010 at 11:55 PM, Rabin Vincent <rabin@rab.in> wrote:
> > Include sched.h in the files implementing sched_clock() and ensure that
> > any functions called from sched_clock() have the notrace annotation.
On Sat, Nov 13, 2010 at 12:14:51AM +0530, Rabin Vincent wrote:
> CC'd some mach maintainers. I can split this up if needed,
> since these bits can be applied independently from the rest
> of the patches in the series.
I've split it up anyway, since tegra and nomadik have since fixed it
themselves while reworking their sched_clock() implementations (and
there are probably others who need to do this), and I missed a couple of
functions in omap and u300 in the first patch.
next prev parent reply other threads:[~2010-11-19 16:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 18:25 [PATCH 1/6] ARM: ensure sched_clock() and children are notrace Rabin Vincent
2010-11-06 18:25 ` Rabin Vincent
2010-11-06 18:25 ` [PATCH 2/6] ARM: place C irq handlers in IRQ_ENTRY for ftrace Rabin Vincent
2010-11-06 18:25 ` Rabin Vincent
2010-11-06 18:25 ` [PATCH 3/6] ARM: ftrace: use gas macros to avoid code duplication Rabin Vincent
2010-11-06 18:25 ` Rabin Vincent
2010-11-06 18:25 ` [PATCH 4/6] ARM: ftrace: function graph tracer support Rabin Vincent
2010-11-06 18:25 ` Rabin Vincent
2010-11-06 18:25 ` [PATCH 5/6] ARM: ftrace: graph tracer + dynamic ftrace Rabin Vincent
2010-11-06 18:25 ` Rabin Vincent
2010-11-06 18:25 ` [PATCH 6/6] ARM: ftrace: enable function graph tracer Rabin Vincent
2010-11-06 18:25 ` Rabin Vincent
2010-11-06 19:06 ` Catalin Marinas
2010-11-06 19:06 ` Catalin Marinas
2010-11-08 9:18 ` Uwe Kleine-König
2010-11-08 9:18 ` Uwe Kleine-König
2010-11-08 10:42 ` Catalin Marinas
2010-11-08 10:42 ` Catalin Marinas
2010-11-09 13:46 ` Rabin Vincent
2010-11-09 13:46 ` Rabin Vincent
2010-11-09 14:22 ` Catalin Marinas
2010-11-09 14:22 ` Catalin Marinas
2010-11-12 18:44 ` [PATCH 1/6] ARM: ensure sched_clock() and children are notrace Rabin Vincent
2010-11-12 18:44 ` Rabin Vincent
2010-11-19 16:09 ` Rabin Vincent [this message]
2010-11-19 16:09 ` Rabin Vincent
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=20101119160849.GA21870@debian \
--to=rabin@rab.in \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.