[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150325090926.GA696@gmail.com>
Date: Wed, 25 Mar 2015 10:09:26 +0100
From: Ingo Molnar <mingo@...nel.org>
To: John Stultz <john.stultz@...aro.org>
Cc: lkml <linux-kernel@...r.kernel.org>,
Daniel Thompson <daniel.thompson@...aro.org>,
Russell King <linux@....linux.org.uk>,
Will Deacon <will.deacon@....com>,
Catalin Marinas <catalin.marinas@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Stephen Boyd <sboyd@...eaurora.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 0/5] Arch-generic sched_clock NMI safety and
optimizations for -tip
* John Stultz <john.stultz@...aro.org> wrote:
> Ingo, Peter, Thomas,
>
> The following patches from Daniel extend the arch-generic sched_clock
> implementation so that it can be safely called from NMI (or FIQ on ARM)
> context. They also optimize the sched_clock logic to improve cache
> performance. I wanted to send them along so they could be queued in
> -tip for 4.1.
Hm, the first patch does not apply to tip:timers/core, as it conflicts
with:
fb82fe2fe858 clocksource: Add 'max_cycles' to 'struct clocksource'
362fde041037 clocksource: Simplify the logic around clocksource wrapping safety margins
Mind resending your latest queue as patches, on top of tip:timers/core
or tip:master?
Thanks,
Ingo
--
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