From: Linus Torvalds <torvalds@linux-foundation.org>
To: Len Brown <lenb@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"Michael K. Johnson" <johnsonm@rpath.com>,
Justin Forbes <jmforbes@linuxtx.org>,
Jordan Hargrave <Jordan_Hargrave@dell.com>,
Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [GIT PULL] x86 setup BIOS workarounds
Date: Thu, 2 Apr 2009 12:31:15 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904021227060.4130@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0904020017480.4657@localhost.localdomain>
On Thu, 2 Apr 2009, Len Brown wrote:
>
> Yes, this expects old BIOS to always return 20.
Do you have any reason to expect that all BIOS'es are bug-free in this
area?
That would be a first.
We already check for other error cases where the BIOS didn't do the right
thing in other ways in its e820 routine, or clobbered the wrogn registers
or whatever. Why would you expect that the return value would always be
ok?
> No, it does not expect old BIOS to have any particular value
> in buf.ext_flags -- since that is examined only for size > 20.
The point is, that expectation that the BIOS returns 20 seems very
unreasonable. BIOS writers tend to have been on pain medication for so
long that they can hardly remember their own name, much less actually make
sure they follow all the documentation.
Now, if Windows has actually _depended_ on the right return value since
Win95, that would be a good, strong argument.
Because that's the only case where we can pretty much depend on BIOS
writers get things right - if Windows doesn't boot when they get it wrong.
As far as I can tell, that has always been the only real quality assurance
for most BIOS'es.
Linus
prev parent reply other threads:[~2009-04-02 19:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200904011640.n31GeD0m008691@voreg.hos.anvin.org>
2009-04-02 4:15 ` [GIT PULL] x86 setup BIOS workarounds Len Brown
2009-04-02 20:07 ` H. Peter Anvin
[not found] ` <alpine.LFD.2.00.0904011115210.4130@localhost.localdomain>
2009-04-02 4:26 ` Len Brown
2009-04-02 19:31 ` Linus Torvalds [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=alpine.LFD.2.00.0904021227060.4130@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=Jordan_Hargrave@dell.com \
--cc=hpa@zytor.com \
--cc=jmforbes@linuxtx.org \
--cc=johnsonm@rpath.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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