From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: sched_clock: allow sched_clock to be selected at runtime
Date: Thu, 11 Aug 2011 09:49:06 +0100 [thread overview]
Message-ID: <20110811084906.GA2732@pulham.picochip.com> (raw)
In-Reply-To: <20110811082515.GB4775@n2100.arm.linux.org.uk>
On Thu, Aug 11, 2011 at 09:25:15AM +0100, Russell King - ARM Linux wrote:
> On Wed, Aug 10, 2011 at 12:49:07PM +0100, Jamie Iles wrote:
> > Tested on my 1176 platform and works nicely. However, shouldn't the
> > read functions still be marked notrace so they don't appear in ftrace
> > output?
> >
> > On my (out of tree) platform, omitting notrace and having all of the
> > ftrace bootup tests results in a hard lockup. Annotating the read
> > function resolves this.
>
> Why not also convert ftrace to use clocksources ?
I can't say I know enough about ftrace to say what the implications of
that would be (other than a dependency on all platforms having a
suitable clocksource).
Jamie
prev parent reply other threads:[~2011-08-11 8:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 17:13 [RFC PATCH] ARM: sched_clock: allow sched_clock to be selected at runtime Marc Zyngier
2011-08-09 20:54 ` Linus Walleij
2011-08-09 21:20 ` Rob Herring
2011-08-09 21:28 ` Eric Miao
2011-08-09 21:33 ` Russell King - ARM Linux
2011-08-10 8:28 ` Marc Zyngier
2011-08-10 8:52 ` Russell King - ARM Linux
2011-08-10 8:59 ` Marc Zyngier
2011-08-10 7:13 ` Linus Walleij
2011-08-10 11:49 ` Jamie Iles
2011-08-10 14:16 ` Marc Zyngier
2011-08-11 8:25 ` Russell King - ARM Linux
2011-08-11 8:49 ` Jamie Iles [this message]
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=20110811084906.GA2732@pulham.picochip.com \
--to=jamie@jamieiles.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).