From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Matt Sealey <matt@genesi-usa.com>
Cc: John Stultz <john.stultz@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux ARM Kernel ML <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: One of these things (CONFIG_HZ) is not like the others..
Date: Tue, 22 Jan 2013 00:02:41 +0000 [thread overview]
Message-ID: <20130122000241.GE23505@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAKGA1b=wDE9ujby_gcoHJudsG=JbWDdNRo+thCe8BhoJLi+B5Q@mail.gmail.com>
On Mon, Jan 21, 2013 at 05:30:31PM -0600, Matt Sealey wrote:
> But it would effectively stop users drinking kool-aid.. if you set
> your HZ to something stupid, you don't even get a kernel to build, and
> certainly don't get to boot past the first 40 lines of boot messages..
> I think most people would rather a build error, or a runtime
> unmistakable, unmissable warning than a subtle and almost
> imperceptible skew in NTP synchronization, to use your example.
1. a kernel which doesn't build. What do you think both Arnd and myself
have been doing for the last few years, building such things as
random configurations and such like, finding stuff that doesn't work
and fixing the kernel so that we end up with _NO_ configuration which
fails to build.
Are you seriously about to tell us that we're wasting our time and we
should just let the kernel build fail in all horrid sorts of ways?
2. As for NTP behaviour... well, have you ever experienced a system where
NTP has to keep doing step corrections on the time of day, where some
steps (eg, backwards) cause services to quit because time of day must
be monotonic...
What you're proposing is that we litter the ARM arch with all sorts of
tests for CONFIG_HZ and #error out on ones that don't make sense. I
think you're smoking crack.
What I think is that we should _not_ allow CONFIG_HZ to be set to
anything which isn't appropriate for the platforms - or indeed the
reverse. That's going to be extremely difficult to do with multi-arch
because it's effectively a two-way dependency.
I don't think we can do that with kernel/Kconfig.hz unless we introduce
another layer of permissive configurations for the HZ_1000... etc, but
I'm not sure that anyone outside ARM would like even that.
next prev parent reply other threads:[~2013-01-22 0:07 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 20:01 One of these things (CONFIG_HZ) is not like the others Matt Sealey
2013-01-21 20:41 ` Arnd Bergmann
2013-01-21 21:00 ` John Stultz
2013-01-21 21:12 ` Russell King - ARM Linux
2013-01-21 22:18 ` John Stultz
2013-01-21 22:44 ` Russell King - ARM Linux
2013-01-22 8:27 ` Arnd Bergmann
2013-01-21 22:20 ` Matt Sealey
2013-01-21 22:42 ` Russell King - ARM Linux
2013-01-21 23:23 ` Matt Sealey
2013-01-21 23:49 ` Russell King - ARM Linux
2013-01-22 0:09 ` Matt Sealey
2013-01-22 0:26 ` Matt Sealey
2013-01-21 21:14 ` Matt Sealey
2013-01-21 22:36 ` John Stultz
2013-01-21 22:49 ` Russell King - ARM Linux
2013-01-21 22:54 ` Matt Sealey
2013-01-21 23:13 ` Russell King - ARM Linux
2013-01-21 23:30 ` Matt Sealey
2013-01-22 0:02 ` Russell King - ARM Linux [this message]
2013-01-22 0:38 ` John Stultz
2013-01-22 0:51 ` John Stultz
2013-01-22 1:06 ` Matt Sealey
2013-01-22 1:18 ` Russell King - ARM Linux
2013-01-22 1:56 ` Matt Sealey
2013-01-22 1:31 ` John Stultz
2013-01-22 2:10 ` Matt Sealey
2013-01-31 21:31 ` Thomas Gleixner
2013-01-21 21:02 ` Matt Sealey
2013-01-21 22:30 ` Arnd Bergmann
2013-01-21 22:45 ` Russell King - ARM Linux
2013-01-21 23:01 ` Matt Sealey
2013-01-21 21:03 ` Russell King - ARM Linux
2013-01-21 23:23 ` Tony Lindgren
2013-01-22 6:23 ` Santosh Shilimkar
2013-01-22 9:31 ` Arnd Bergmann
2013-01-22 10:14 ` Santosh Shilimkar
2013-01-22 14:51 ` Russell King - ARM Linux
2013-01-22 15:05 ` Santosh Shilimkar
2013-01-28 6:08 ` Santosh Shilimkar
2013-01-29 0:01 ` John Stultz
2013-01-29 6:43 ` Santosh Shilimkar
2013-01-29 10:06 ` Russell King - ARM Linux
2013-01-29 18:43 ` John Stultz
2013-01-22 17:31 ` Arnd Bergmann
2013-01-22 18:59 ` John Stultz
2013-01-22 21:52 ` Tony Lindgren
2013-01-23 5:18 ` Santosh Shilimkar
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=20130122000241.GE23505@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arnd@arndb.de \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@genesi-usa.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).