From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/NOT FOR MERGING] HACK: add global/private timers for A9
Date: Wed, 3 Jun 2015 16:28:21 -0500 [thread overview]
Message-ID: <20150603212821.GH6042@saruman.tx.rr.com> (raw)
In-Reply-To: <20150603210455.GD6042@saruman.tx.rr.com>
On Wed, Jun 03, 2015 at 04:04:55PM -0500, Felipe Balbi wrote:
> On Wed, Jun 03, 2015 at 10:55:27PM +0200, Arnd Bergmann wrote:
> > On Wednesday 03 June 2015 15:32:45 Felipe Balbi wrote:
> > >
> > > Hi Tony and Russell,
> > >
> > > AM43xx, even though it's a single processor A9, it still has TWD and global
> > > timer. I was doing some profiling with RT v4.0 and latency is 3.5x lower just
> > > by switching from gptimer to twd/global.
> > >
> > > The only problem is that currently, is_smp() check prevents me from using twd
> > > with AM43xx (that's why it's commented below, for testing purposes).
> > >
> > > In the hopes that we can start a, hopefully, small thread around the subject,
> > > I'm sending this HACK which I used to get TWD and global timer enabled so I
> > > could measure latencies with cyclictest.
> > >
> > > Is it so that TWD shouldn't be available on UP integrations of ARM's Cortex-A
> > > processors ?
> > >
> > >
> >
> > I wondered about this recently when looking at something unrelated
> > and noticed that the check had been introduced as part of
> > 904464b91eca8 ("ARM: 7655/1: smp_twd: make twd_local_timer_of_register()
> > no-op for nosmp").
> >
> > I suspect this was just the wrong fix at the time, and that the
> > real culprit is either alloc_percpu() or request_percpu_irq()
> > getting called too early on a machine without SMP support.
> >
> > Possibly the problem is already resolved independently, if you
> > didn't run into it.
>
> no, no splats, nothing at all. See [1]
>
> [1] http://hastebin.com/helekubutu
Adding Shawn
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150603/5c457aaf/attachment.sig>
next prev parent reply other threads:[~2015-06-03 21:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 20:32 [RFC/NOT FOR MERGING] HACK: add global/private timers for A9 Felipe Balbi
2015-06-03 20:44 ` Tony Lindgren
2015-06-03 20:55 ` Arnd Bergmann
2015-06-03 21:04 ` Felipe Balbi
2015-06-03 21:28 ` Felipe Balbi [this message]
2015-06-03 21:41 ` Stephen Boyd
2015-06-03 21:54 ` Felipe Balbi
2015-06-04 9:46 ` Mason
2015-06-04 19:05 ` Felipe Balbi
2015-06-04 20:08 ` Felipe Balbi
2015-06-04 20:18 ` Felipe Balbi
2015-06-04 20:29 ` Felipe Balbi
2015-06-04 22:20 ` Stephen Boyd
2015-06-05 15:42 ` Felipe Balbi
2015-06-04 20:32 ` Mason
2015-06-04 20:37 ` Felipe Balbi
2015-06-04 21:00 ` Mason
2015-06-04 21:46 ` Tony Lindgren
2015-06-03 22:26 ` Tony Lindgren
2015-06-04 3:45 ` Felipe Balbi
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=20150603212821.GH6042@saruman.tx.rr.com \
--to=balbi@ti.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