[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51AD32A4.5070609@linaro.org>
Date: Mon, 03 Jun 2013 17:19:48 -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,
Russell King <linux@....linux.org.uk>, arm@...nel.org,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCHv2 0/6] Make ARM's sched_clock generic + 64 bit friendly
On 06/01/2013 11:39 PM, Stephen Boyd wrote:
> This is mostly a resend of a patch series I sent a little over a month
> ago. I've reordered the patches so that John can pick up the first three
> and get a generic sched_clock layer without having to take the 64 bit
> patches. The last three patches add 64 bit support and move the architected
> timers on ARM64 and ARM to use it.
Yea, so from the initial look over it, I think I'm happy with queuing
the first three patches, although I'd like to get some acks from arm
folks on at least the first two, just so no one is surprised with it
going through the -tip tree.
It looks like the arm64 bit stuff needs a few more iterations w/
Russell, so I'll not touch those.
We still have a ways to go to consolidate x86 into this (need to handle
pv hooks), but it should provide a base to get some of the simpler
arches sharing the same infrastructure.
Also I suspect we can maybe further combine this with the
kernel/sched/clock.c code, but I think this is a good start for now.
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