[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51E88170.3080505@linaro.org>
Date: Thu, 18 Jul 2013 16:59:44 -0700
From: John Stultz <john.stultz@...aro.org>
To: Stephen Boyd <sboyd@...eaurora.org>
CC: linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Thomas Gleixner <tglx@...utronix.de>,
Russell King <linux@....linux.org.uk>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Christopher Covington <cov@...eaurora.org>,
Barry Song <Baohua.Song@....com>,
Fabio Estevam <fabio.estevam@...escale.com>,
Gregory CLEMENT <gregory.clement@...e-electrons.com>,
Jingchang Lu <b35083@...escale.com>,
Kukjin Kim <kgene.kim@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Linus Walleij <linus.walleij@...aro.org>,
Shawn Guo <shawn.guo@...aro.org>,
Srinidhi Kasagar <srinidhi.kasagar@...ricsson.com>,
Stephen Warren <swarren@...dotorg.org>,
Tomasz Figa <t.figa@...sung.com>
Subject: Re: [PATCH v4 00/17] 64-bit friendly generic sched_clock()
On 07/18/2013 04:21 PM, Stephen Boyd wrote:
> This patchset adds support for 64 bit counters in the generic
> sched_clock code and converts drivers over to use it. Based
> on v3.11-rc1.
>
> Changes since v3:
> * Move to use seqcount to fix issues with 64-bit cyc counters
> * Move to hrtimer to fix underflow/overflow errors in wraparound
> calculation
> * Use of 1 hour in clocks_calc_mult_shift
> * Converted over drivers in drivers/clocksource
I've not been able to take a deep review yet, but this looks pretty much
like what we discussed last week, so I'm happy with it so far. Has this
gotten much testing (on both 32 and 64bit systems?)
One detail: Most of this is likely to go in via tip/timers/core, but the
5/17 "arch_timer: Move to generic sched_clock" will need some
synchronization with Catalin to make sure its ok to go in via tip. Not
sure what other arm64 changes are pending that would depend or collide
with that change.
thanks
-john
--
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