From: Tim Bird <tim.bird@am.sony.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Todd Poynor <tpoynor@mvista.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dsingleton@mvista.com, vda@port.imtp.ilyichevsk.odessa.ua,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH] Configure IDE probe delays
Date: Mon, 02 Aug 2004 14:56:55 -0700 [thread overview]
Message-ID: <410EB8A7.1090101@am.sony.com> (raw)
In-Reply-To: <1091226922.5083.13.camel@localhost.localdomain>
Denis Vlasenko wrote:
> Crowd of "my old crapbox no longer boots with newer kernel, wtf?" people
> won't be happy at all.
>
> + ide_delay = simple_strtoul(s+10,NULL,0);
> + printk(" : Delay set to %dms\n", ide_delay);
> + return 1;
>
> Can we have a bit louder warning here?
We can make this even stronger if desired.
Alan Cox wrote:
> On Gwe, 2004-07-30 at 20:11, Todd Poynor wrote:
>
>>IDE initialization and probing makes numerous calls to sleep for 50
>>milliseconds while waiting for the interface to return probe status and
>>such.
>
>
> Please make it taint the kernel if you do that so we can ignore all the
> bug reports.
We can certainly make the warning louder as Denis suggests, and also
make the wording in the documentation stronger, like so...
+ "ide-delay=xx" : set delay in milliseconds for initialization and
+ probing. Defaults to 50ms. Use at your own risk. Please
+ do not report ANY problems to kernel developers if using a
+ non-default setting.
If needed, I'd be willing to taint the kernel to reduce the burden
of related bug reports. I'm a little concerned that tainting conveys
a meaning of GPL conformance questionability, which would not be the
case here. (Just configuration questionability... ;-)
This is primarily to support embedded systems with known hardware, but
I *DO* see the need to avoid having desktop people experiment with it
and make themselves (and by transitivity kernel developers) unhappy.
This is, admittedly, introducing a gun which one might use to shoot
one's own foot. However, in my testing these delays accounted
for about 70% of total kernel bootup time, and this is a pretty easy
way to "fix" it. I know many companies are very willing to bear
the burden of testing this out on their hardware before shipping
products (Sony would), in exchange for the dramatic bootup time
savings.
I'm still considering Jeff's comment, and I'll respond to that separately.
=============================
Tim Bird
Architecture Group Co-Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
E-mail: tim.bird@am.sony.com
=============================
next prev parent reply other threads:[~2004-08-02 21:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 19:11 [PATCH] Configure IDE probe delays Todd Poynor
2004-07-30 21:36 ` Lee Revell
2004-07-30 22:35 ` Alan Cox
2004-07-31 0:12 ` Lee Revell
[not found] ` <200407311434.59604.vda@port.imtp.ilyichevsk.odessa.ua>
2004-07-31 18:00 ` Lee Revell
2004-08-27 17:45 ` Greg Stark
2004-08-27 17:53 ` Lee Revell
2004-08-27 18:05 ` Bartlomiej Zolnierkiewicz
2004-08-27 18:08 ` Lee Revell
2004-08-27 18:59 ` Bartlomiej Zolnierkiewicz
2004-09-01 13:20 ` Mark Lord
2004-09-01 14:43 ` Jeff Garzik
2004-09-01 15:30 ` Mark Lord
2004-09-01 15:36 ` Mark Lord
2004-09-01 19:36 ` Lee Revell
2004-09-01 18:42 ` Alan Cox
2004-09-01 15:06 ` Alan Cox
2004-09-01 19:08 ` Lee Revell
2004-09-02 16:04 ` Mark Lord
2004-09-01 15:40 ` Bartlomiej Zolnierkiewicz
2004-07-31 18:06 ` Lee Revell
2004-07-31 19:35 ` Alan Cox
2004-07-31 21:35 ` Lee Revell
2004-07-31 21:44 ` Jeff Garzik
2004-07-31 22:12 ` Lee Revell
2004-08-04 17:30 ` Anthony de Boer
2004-08-05 21:39 ` Tim Bird
2004-07-31 0:54 ` Jeff Garzik
2004-08-03 17:47 ` Mark Lord
2004-08-06 15:48 ` Jeff Garzik
2004-08-06 19:29 ` Tim Bird
2004-08-06 20:46 ` Todd Poynor
2004-08-02 21:56 ` Tim Bird [this message]
2004-08-02 21:01 ` Alan Cox
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=410EB8A7.1090101@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dsingleton@mvista.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tpoynor@mvista.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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