[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1505220009120.5457@nanos>
Date: Fri, 22 May 2015 00:09:42 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Ezequiel Garcia <ezequiel.garcia@...tec.com>
cc: linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org,
Daniel Lezcano <daniel.lezcano@...aro.org>,
devicetree@...r.kernel.org,
Andrew Bresticker <abrestic@...omium.org>,
James Hartley <james.hartley@...tec.com>,
James Hogan <james.hogan@...tec.com>,
Damien.Horsley@...tec.com, Govindraj.Raja@...tec.com
Subject: Re: [PATCH 6/7] clocksource: Add Pistachio clocksource-only driver
On Thu, 21 May 2015, Ezequiel Garcia wrote:
> On 05/21/2015 07:00 PM, Thomas Gleixner wrote:
> > On Thu, 21 May 2015, Ezequiel Garcia wrote:
> >> +static cycle_t clocksource_read_cycles(struct clocksource *cs)
> >> +{
> >> + u32 counter, overflw;
> >> + unsigned long flags;
> >> +
> >> + raw_spin_lock_irqsave(&lock, flags);
> >
> > Hmm. Is that lock really necessary to read that counter? The
> > clocksource is global. And if its actually used for timekeeping, the
> > lock can get heavy contended.
> >
>
> Yup, it is really (and sadly) necessary. The kernel hangs up completely
> without it when the counter is accesed by more than one CPU.
>
> Apparently, those two timer registers overflow and counter must be read
> atomically.
Welcome to the wonderful world of useless timer hardware.
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists