From: "George Spelvin" <linux@horizon.com>
To: belyshev@depni.sinp.msu.ru, johnstul@us.ibm.com
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux@horizon.com, mingo@elte.hu, tglx@linutronix.de,
ulrich.windl@rz.uni-regensburg.de, williams@redhat.com,
zippel@linux-m68k.org
Subject: Re: [PATCH] tsc_khz= boot option to avoid TSC calibration variance
Date: 13 May 2009 14:45:16 -0400 [thread overview]
Message-ID: <20090513184516.19020.qmail@science.horizon.com> (raw)
In-Reply-To: <87d4aejw5b.fsf@depni.sinp.msu.ru>
> No, it won't, because...
> <cde snippet>
> ... of this "if".
>
> Please *please* don't set arbitrary limits. Just use user supplied value.
>
> Or at the very least print big red warning if you are going to ignore a user
> supplied option (and have another tsc_khz_really= option to override faulty
> calibration routine).
I'd like to disagree. The calibration is accurate and reliable.
It has worked without any override for millions of users for many
years. What is the plausible reason to need to set it to a wildly
divergent value?
On the other hand, what if my CPU gets fried and I replace it with one
with a different clock multiplier? Or the motherboard fries and I move
the boot hard drive to a different machine? That's a situation that I
have found myself in. And I don't want to figure out how to edit the
LILO options before booting the machine, even if I remember to do it
at all; this is an emergency replacement.
In such a case, having the kernel believe the command line could result
in it not booting, or the system not working properly.
Much better that it basically work, even if some fine-tuning remains
to be done.
And that's the idea: this is a fine-tuning option. If the calibration
says the option value is grossly wrong, then something strange has
happened, and the kernel calibration value is safer.
If you think a coarse-tuning option is required, I can extend the patch
so that a trailing ! (e.g. "tsc_khz=3000000!") disables the sanity check.
Bit I'd still like to see an argument for why it is required. Remember,
it would be far better to make the kernel self-calibration more accurate,
so people don't even have to use this option. It's only there because
it's the simplest way (simplest for the lazy programmer, not the user!)
to guarantee getting exactly the same value each boot.
>From a *user* point of view, I'd rather the kernel did it automagically
and I didn't need to futz with the kernel command line at all.
prev parent reply other threads:[~2009-05-13 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 2:12 john stultz
2009-05-12 8:36 ` Ulrich Windl
2009-05-12 22:26 ` john stultz
2009-05-12 22:42 ` Thomas Gleixner
2009-05-12 23:02 ` john stultz
2009-05-13 9:41 ` Petri Kaukasoina
2009-05-13 7:59 ` Ulrich Windl
2009-05-13 9:23 ` Petri Kaukasoina
2009-05-13 10:06 ` Petri Kaukasoina
2009-05-12 13:20 ` Serge Belyshev
2009-05-12 23:31 ` john stultz
2009-05-13 18:45 ` George Spelvin [this message]
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=20090513184516.19020.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=akpm@linux-foundation.org \
--cc=belyshev@depni.sinp.msu.ru \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=ulrich.windl@rz.uni-regensburg.de \
--cc=williams@redhat.com \
--cc=zippel@linux-m68k.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
Powered by JetHome