From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Adam Kropelin <akropel1@rochester.rr.com>,
Tim Bird <tim.bird@am.sony.com>,
CE Linux Developers List <celinux-dev@tree.celinuxforum.org>,
Todd Poynor <tpoynor@mvista.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH] preset loops_per_jiffy for faster booting
Date: Sat, 10 Jul 2004 13:19:30 -0500 [thread overview]
Message-ID: <200407101319.31147.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040710142800.A5093@mail.kroptech.com>
On Saturday 10 July 2004 01:28 pm, Adam Kropelin wrote:
> + Note that on SMP systems the preset will be applied to all CPUs
> + which will cause problems if for some reason your CPUs need
> + significantly divergent settings.
> +
> + If unsure, set this to 0. An incorrect value will cause delays in
> + the kernel to be wrong, leading to unpredictable I/O errors and
> + other breakage. Although unlikely, in the extreme case this might
> + damage your hardware.
>
Note that it may also not work correctly on laptops that switch frequency
when working on battery/AC. Also one needs to be careful when changing
timesource (pit, tsc, pm, hpet). And always look out for timer code changes
in next version of kernel. Does 250 ms worth all this pain?
--
Dmitry
next prev parent reply other threads:[~2004-07-10 18:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 19:25 [PATCH] preset loops_per_jiffy for faster booting Tim Bird
2004-07-09 22:24 ` Adam Kropelin
2004-07-09 23:35 ` Adam Kropelin
2004-07-10 0:20 ` Tim Bird
2004-07-10 2:01 ` Adam Kropelin
2004-07-10 2:01 ` Todd Poynor
2004-07-10 15:42 ` Adam Kropelin
2004-07-10 14:41 ` [Celinux-dev] " Geert Uytterhoeven
2004-07-10 15:22 ` Adam Kropelin
2004-07-10 15:54 ` Adam Kropelin
2004-07-10 18:28 ` Adam Kropelin
2004-07-10 18:19 ` Dmitry Torokhov [this message]
2004-07-10 20:14 ` Adam Kropelin
2004-07-11 1:25 ` Andrew Morton
2004-07-11 3:44 ` Adam Kropelin
2004-07-11 4:38 ` Andrew Morton
2004-07-12 17:31 ` Tim Bird
2004-07-11 4:51 ` Dmitry Torokhov
2004-07-11 4:58 ` Karim Yaghmour
2004-07-11 5:19 ` Dmitry Torokhov
2004-07-11 5:27 ` Andrew Morton
2004-07-11 7:46 ` Geert Uytterhoeven
2004-07-11 7:51 ` Andrew Morton
2004-07-11 13:41 ` Adam Kropelin
2004-07-12 18:52 ` Tim Bird
2004-07-12 19:32 ` Adam Kropelin
2004-07-12 22:41 ` Tim Bird
2004-07-13 19:24 ` Bartlomiej Zolnierkiewicz
2004-07-12 17:50 ` Tim Bird
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=200407101319.31147.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=akropel1@rochester.rr.com \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.com \
--cc=tpoynor@mvista.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