[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1374692894-27202-1-git-send-email-fweisbec@gmail.com>
Date: Wed, 24 Jul 2013 21:08:12 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Li Zhong <zhong@...ux.vnet.ibm.com>,
Steven Rostedt <rostedt@...dmis.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Borislav Petkov <bp@...en8.de>, Mike Galbraith <efault@....de>,
Kevin Hilman <khilman@...aro.org>
Subject: [GIT PULL] nohz fixes
Ingo,
Please pull the timers/urgent branch that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
timers/urgent
Just one thing you need to know: you reported me that the warning was
"too much" to tell the user that he can't use full dynticks due to unstable tsc.
I discussed that with Steve and we concluded that we could keep the warning but
only trigger it if the user explicitly wants to use the full dynticks which we
deduce by checking if he filled the nohz_full= boot parameter or he selected
CONFIG_NO_HZ_FULL_ALL. This way we make sure that the user knows what's going
on but only if he really expected to use it.
If you still consider the tainting warning to be too much a hammer, even if only
real users are warned, then tell me and I'll change that to some way you
prefer.
Thanks,
Frederic
---
Li Zhong (1):
nohz: fix compile warning in tick_nohz_init()
Steven Rostedt (1):
nohz: Do not warn about unstable tsc unless user uses nohz_full
kernel/time/tick-sched.c | 5 ++---
1 files changed, 2 insertions(+), 3 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