From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Rabin Vincent <rabin@rab.in>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Eric Miao <eric.y.miao@gmail.com>,
Erik Gilling <konkers@android.com>,
Nicolas Pitre <nico@fluxnic.net>,
Tony Lindgren <tony@atomide.com>,
linux-tegra@vger.kernel.org, Colin Cross <ccross@android.com>,
Olof Johansson <olof@lixom.net>, Imre Kaloz <kaloz@openwrt.org>,
Lennert Buytenhek <kernel@wantstofly.org>,
Krzysztof Halasa <khc@pm.waw.pl>
Subject: Re: [PATCH] ARM: ensure all sched_clock() implementations are notrace marked
Date: Thu, 16 Dec 2010 15:57:50 +0000 [thread overview]
Message-ID: <20101216155750.GA28126@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTimGHSqO=QwESp98UBK28yawdiq+kURU=nwau27G@mail.gmail.com>
On Thu, Dec 16, 2010 at 08:42:23PM +0530, Rabin Vincent wrote:
> On Thu, Dec 16, 2010 at 1:48 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > ftrace requires sched_clock() to be notrace. Ensure that all
> > implementations are so marked.
> >
> > Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
>
> It does seem better to have all of them explicity annotated anyway, even
> if it not required in most of the cases because they include
> <linux/sched.h> and the annotation in the declaration takes effect.
Firstly, we shouldn't be relying upon that, and secondly, everywhere which
defines sched_clock() should already be including linux/sched.h to avoid
the sparse error. It sounds like there's also an exercise to make sure
that is the case.
> Note that in order for this to be fully effective, all functions called
> from sched_clock() need to be notrace too. OMAP and u300 miss this.
Yes, OMAP still suffers from this.
However, I assume you haven't looked at the u300 sched_clock conversion
patch which is part of a follow-on series on lakml? It sorts u300 out
in that regard.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ensure all sched_clock() implementations are notrace marked
Date: Thu, 16 Dec 2010 15:57:50 +0000 [thread overview]
Message-ID: <20101216155750.GA28126@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTimGHSqO=QwESp98UBK28yawdiq+kURU=nwau27G@mail.gmail.com>
On Thu, Dec 16, 2010 at 08:42:23PM +0530, Rabin Vincent wrote:
> On Thu, Dec 16, 2010 at 1:48 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > ftrace requires sched_clock() to be notrace. ?Ensure that all
> > implementations are so marked.
> >
> > Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
>
> It does seem better to have all of them explicity annotated anyway, even
> if it not required in most of the cases because they include
> <linux/sched.h> and the annotation in the declaration takes effect.
Firstly, we shouldn't be relying upon that, and secondly, everywhere which
defines sched_clock() should already be including linux/sched.h to avoid
the sparse error. It sounds like there's also an exercise to make sure
that is the case.
> Note that in order for this to be fully effective, all functions called
> from sched_clock() need to be notrace too. OMAP and u300 miss this.
Yes, OMAP still suffers from this.
However, I assume you haven't looked at the u300 sched_clock conversion
patch which is part of a follow-on series on lakml? It sorts u300 out
in that regard.
next prev parent reply other threads:[~2010-12-16 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 8:18 [PATCH] ARM: ensure all sched_clock() implementations are notrace marked Russell King - ARM Linux
2010-12-16 8:18 ` Russell King - ARM Linux
2010-12-16 15:12 ` Rabin Vincent
2010-12-16 15:12 ` Rabin Vincent
2010-12-16 15:57 ` Russell King - ARM Linux [this message]
2010-12-16 15:57 ` Russell King - ARM Linux
2010-12-16 16:22 ` Rabin Vincent
2010-12-16 16:22 ` Rabin Vincent
2010-12-16 17:03 ` Russell King - ARM Linux
2010-12-16 17:03 ` Russell King - ARM Linux
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=20101216155750.GA28126@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=ccross@android.com \
--cc=eric.y.miao@gmail.com \
--cc=kaloz@openwrt.org \
--cc=kernel@wantstofly.org \
--cc=khc@pm.waw.pl \
--cc=konkers@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=olof@lixom.net \
--cc=rabin@rab.in \
--cc=tony@atomide.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 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.