From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Li Zhong <zhong@linux.vnet.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@alien8.de>, Mike Galbraith <efault@gmx.de>,
Kevin Hilman <khilman@linaro.org>
Subject: Re: [GIT PULL] nohz fixes
Date: Thu, 25 Jul 2013 23:04:22 +0200 [thread overview]
Message-ID: <20130725210422.GA18254@gmail.com> (raw)
In-Reply-To: <1374692894-27202-1-git-send-email-fweisbec@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> 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(-)
Pulled, thanks Frederic!
Ingo
next prev parent reply other threads:[~2013-07-25 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 19:08 [GIT PULL] nohz fixes Frederic Weisbecker
2013-07-24 19:08 ` [PATCH 1/2] nohz: Do not warn about unstable tsc unless user uses nohz_full Frederic Weisbecker
2013-07-24 19:08 ` [PATCH 2/2] nohz: fix compile warning in tick_nohz_init() Frederic Weisbecker
2013-07-25 21:04 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-29 16:39 [GIT PULL] nohz fixes Frederic Weisbecker
2013-05-30 23:38 ` Frederic Weisbecker
2013-05-31 10:02 ` Ingo Molnar
2013-05-14 16:02 [GIT PULL] Nohz fixes Frederic Weisbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130725210422.GA18254@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=zhong@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox