[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140123005624.GC24093@localhost.localdomain>
Date: Thu, 23 Jan 2014 01:56:26 +0100
From: Frederic Weisbecker <fweisbec@...il.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Kevin Hilman <khilman@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Alex Shi <alex.shi@...aro.org>,
Steven Rostedt <rostedt@...dmis.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
John Stultz <john.stultz@...aro.org>
Subject: Re: [GIT PULL] tick: A few more cleanups
On Thu, Jan 16, 2014 at 04:41:48PM +0100, Frederic Weisbecker wrote:
> Ingo,
>
> Please pull the timers/core branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> timers/core
>
> HEAD: 8fe8ff09ce3b5750e1f3e45a1f4a81d59c7ff1f1
>
> ----
> Nothing very exiting, just a bunch of non-critical cleanups for the next merge window:
>
> 1) Make the IRQ tick APIs naming more symetric
>
> 2) Optimize a bit jiffies_lock code coverage
>
> 3) Whitespace fixes from Alex Shi
>
> 4) Fix overflow in scheduler tick max deferment calculation. Given the
> current 1 second max limitation, this bug shouldn't happen in mainline.
> It's rather to prepare for making this value tunable. Or simply in case
> we change the current constant.
>
> Thanks,
> Frederic
> ---
>
> Frederic Weisbecker (2):
> tick: Rename tick_check_idle() to tick_irq_enter()
> nohz: Get timekeeping max deferment outside jiffies_lock
>
> Alex Shi (1):
> nohz_full: fix code style issue of tick_nohz_full_stop_tick
>
> Kevin Hilman (1):
> sched/nohz: Fix overflow error in scheduler_tick_max_deferment()
>
Ping.
>
> include/linux/jiffies.h | 6 ++++++
> include/linux/tick.h | 6 +++---
> kernel/sched/core.c | 2 +-
> kernel/softirq.c | 2 +-
> kernel/time/tick-sched.c | 27 ++++++++++++++-------------
> 5 files changed, 25 insertions(+), 18 deletions(-)
--
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