From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Frederic Weisbecker <fweisbec@gmail.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] nohz: ensure users are aware boot CPU is not NO_HZ_FULL
Date: Thu, 6 Feb 2014 13:33:39 -0500 [thread overview]
Message-ID: <52F3D583.9070208@windriver.com> (raw)
In-Reply-To: <20140131163817.GC21061@localhost.localdomain>
On 14-01-31 11:38 AM, Frederic Weisbecker wrote:
> On Tue, Jan 28, 2014 at 04:06:30PM -0800, Paul E. McKenney wrote:
>> On Tue, Jan 28, 2014 at 12:10:49PM -0500, Paul Gortmaker wrote:
>>> This bit of information is in the Kconfig help text:
>>>
>>> Note the boot CPU will still be kept outside the range to
>>> handle the timekeeping duty.
>>>
>>> However neither the variable NO_HZ_FULL_ALL, or the prompt
>>> convey this important detail, so lets add it to the prompt
>>> to make it more explicitly obvious to the average user.
>>>
>>> Cc: Frederic Weisbecker <fweisbec@gmail.com>
>>> Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
>>> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>>
>> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>>
>>> ---
>>> kernel/time/Kconfig | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/kernel/time/Kconfig b/kernel/time/Kconfig
>>> index 3ce6e8c5f3fc..76a1fbef1fd8 100644
>>> --- a/kernel/time/Kconfig
>>> +++ b/kernel/time/Kconfig
>>> @@ -124,7 +124,7 @@ config NO_HZ_FULL
>>> endchoice
>>>
>>> config NO_HZ_FULL_ALL
>>> - bool "Full dynticks system on all CPUs by default"
>>> + bool "Full dynticks system on all (but boot) CPUs by default"
>
> Looks good. Now we are all using "boot CPU" to refer to the CPU 0, but it may
> not sound that obvious to everyone.
>
> How about: "Full dynticks system on all CPUs by default (expect CPU 0)" ?
Sure, I'll send a v2 with the above, but I'll s/expect/except/ :)
Thanks,
Paul.
--
>
> Sure this is a temporary behaviour until I get the sysidle detection use patchset in shape,
> but indeed worth a big fat warning until we sort it out.
>
> Thanks!
>
>>> depends on NO_HZ_FULL
>>> help
>>> If the user doesn't pass the nohz_full boot option to
>>> --
>>> 1.8.5.2
>>>
>>
next prev parent reply other threads:[~2014-02-06 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 17:10 [PATCH] nohz: ensure users are aware boot CPU is not NO_HZ_FULL Paul Gortmaker
2014-01-29 0:06 ` Paul E. McKenney
2014-01-31 16:38 ` Frederic Weisbecker
2014-02-06 18:33 ` Paul Gortmaker [this message]
2014-02-06 18:36 ` [PATCH v2] " Paul Gortmaker
2014-02-10 16:19 ` Frederic Weisbecker
2014-02-11 15:24 ` Paul E. McKenney
2014-02-26 20:07 ` [tip:timers/core] " tip-bot for Paul Gortmaker
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=52F3D583.9070208@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@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