From: oss@buserror.net (Scott Wood)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/2] ARM64: arch_timer: Work around QorIQ Erratum A-009971
Date: Tue, 12 Apr 2016 00:54:18 -0500 [thread overview]
Message-ID: <1460440458.32510.110.camel@buserror.net> (raw)
In-Reply-To: <570B7486.3080204@arm.com>
On Mon, 2016-04-11 at 10:55 +0100, Marc Zyngier wrote:
> On 11/04/16 03:22, Scott Wood wrote:
> > @@ -52,6 +53,20 @@ extern bool arm_arch_timer_reread;
> > _val; \
> > })
> >
> > +#define ARCH_TIMER_TVAL_REWRITE(pv, val) do { \
> > + u64 _cnt_old, _cnt_new; \
> > + int _timeout = 200; \
> > + do { \
> > + asm volatile("mrs %0, cntvct_el0;" \
> > + "msr cnt" pv "_tval_el0, %2;" \
> > + "mrs %1, cntvct_el0" \
> > + : "=&r" (_cnt_old), "=r" (_cnt_new) \
> > + : "r" (val)); \
> > + _timeout--; \
> > + } while (_cnt_old != _cnt_new && _timeout); \
> > + WARN_ON_ONCE(!_timeout); \
> > +} while (0)
> > +
>
> Given how many times you've written that loop, I'm sure you can have a
> preprocessor macro that will do the right thing.
I did use a preprocessor macro. Are you asking me to consolidate the read and
write macros? That seems like it would create a mess that's worse than an
extra instance of a simple loop.
-Scott
next prev parent reply other threads:[~2016-04-12 5:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 2:22 [RFC PATCH 0/2] ARM/ARM64: arch_timer: QorIQ errata Scott Wood
2016-04-11 2:22 ` [RFC PATCH 1/2] ARM/ARM64: arch_timer: Work around QorIQ Erratum A-008585 Scott Wood
2016-04-11 9:19 ` Will Deacon
2016-04-11 9:52 ` Marc Zyngier
2016-04-12 5:48 ` Scott Wood
2016-04-12 9:07 ` Marc Zyngier
2016-04-13 5:41 ` Scott Wood
2016-04-13 7:36 ` Marc Zyngier
2016-04-13 13:22 ` Rob Herring
2016-04-17 0:58 ` Scott Wood
2016-04-11 2:22 ` [RFC PATCH 2/2] ARM64: arch_timer: Work around QorIQ Erratum A-009971 Scott Wood
2016-04-11 9:55 ` Marc Zyngier
2016-04-12 5:54 ` Scott Wood [this message]
2016-04-12 8:22 ` Marc Zyngier
2016-04-17 1:32 ` Scott Wood
2016-04-18 9:28 ` Marc Zyngier
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=1460440458.32510.110.camel@buserror.net \
--to=oss@buserror.net \
--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.