From: Tim Bird <tim.bird@am.sony.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
Mark Gross <mgross@linux.jf.intel.com>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: ANNOUNCE: CE Linux Forum - Specification V1.0 draft
Date: Wed, 19 May 2004 16:46:08 -0700 [thread overview]
Message-ID: <40ABF1C0.1010804@am.sony.com> (raw)
In-Reply-To: <20040519225729.A28893@flint.arm.linux.org.uk>
Russell King wrote:
> On Wed, May 19, 2004 at 12:30:42PM -0700, Tim Bird wrote:
>
>>The non-normative section of this spec. explains where this was
>>a problem in 2.4, and why it is desirable, from the standpoint of
>>bootup time reduction, to avoid these busywaits.
>
> In this case, it's really a bug that IDE is using a busy wait where it
> should be using a sleeping wait. It's a bug, plain and simple. To
> wrap the bug into "a spec" somehow seems wrong to me, especially when
> it would be far better to report the problem as a bug.
Sometimes it's difficult to discern what the intention or correctness
of a piece of code is, when you have limited experience with the code.
I know, we could have just asked...
>
> Sure, specs make suit-wearing people happy, but that doesn't mean that
> they're appropriate as a bug reporting method. 8)
Agreed. :-) We should probably mutate this into a more general
statement that says "busywaits are not appreciated as a delay mechanism
by drivers on bootup."
=============================
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-05-19 23:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 19:05 ANNOUNCE: CE Linux Forum - Specification V1.0 draft Tim Bird
2004-05-17 19:19 ` Christoph Hellwig
2004-05-17 19:59 ` Tim Bird
2004-05-17 20:42 ` Mark Gross
2004-05-17 20:48 ` Arjan van de Ven
[not found] ` <20040518074854.A7348@infradead.org>
2004-05-18 19:32 ` Mark Gross
2004-05-18 19:56 ` Russell King
2004-05-18 20:45 ` Bartlomiej Zolnierkiewicz
2004-05-18 20:00 ` viro
2004-05-19 19:30 ` Tim Bird
2004-05-19 21:57 ` Russell King
2004-05-19 22:02 ` Jeff Garzik
2004-05-19 23:46 ` Tim Bird [this message]
2004-05-19 22:08 ` Theodore Ts'o
2004-05-19 23:37 ` Tim Bird
2004-05-17 21:22 ` Tim Bird
2004-05-19 15:27 ` Adrian Bunk
2004-05-19 16:59 ` Tim Bird
2004-05-19 20:16 ` Adrian Bunk
2004-05-19 20:38 ` Tim Bird
2004-05-19 20:48 ` Nicolas Pitre
2004-05-19 22:00 ` Russell King
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=40ABF1C0.1010804@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.jf.intel.com \
--cc=rmk+lkml@arm.linux.org.uk \
/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