From: Len Brown <lenb@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.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, 02 Apr 2009 00:26:11 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904020017480.4657@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0904011115210.4130@localhost.localdomain>
On Wed, 1 Apr 2009, Linus Torvalds wrote:
>
>
> On Wed, 1 Apr 2009, H. Peter Anvin wrote:
> >
> > implements handling for the backwards-incompatible(!) E820 handling in
> > ACPI 3.
>
> I am _extremely_ nervous about this one.
>
> You do
>
> size = sizeof buf; /* ACPI-3 size */
> asm(.. "+c" (size) /* size might change */
> ..
> if (size > 20 && !(buf.ext_flags & 1))
> continue;
>
> ie you are expecting that _all_ old pre-ACPI-3 BIOSES will always set size
> to 20, or always write a low-bit-set value to that extended flag field
> that doesn't even exist previously.
Yes, this expects old BIOS to always return 20.
No, it does not expect old BIOS to have any particular value
in buf.ext_flags -- since that is examined only for size > 20.
> I don't think that's likely true. Quite frankly, I'd expect a number of
> BIOSen to entirely ignore %ecx, since it's irrelevant (it _has_ to be
> bigger than 20 anyway on entry, and I doubt anybody really ever bothered
> to test that it's 20 on exit).
>
> So at a _minimum_, I'd suggest that we set bug.ext_flags to 1 before the
> call - so that if some random BIOS just leaves %ecx unchanged, it won't
> mean that the area just gets ignored as a ACPI-3 entry.
Good idea.
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-04-02 4:26 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 [this message]
2009-04-02 19:31 ` Linus Torvalds
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.0904020017480.4657@localhost.localdomain \
--to=lenb@kernel.org \
--cc=Jordan_Hargrave@dell.com \
--cc=hpa@zytor.com \
--cc=jmforbes@linuxtx.org \
--cc=johnsonm@rpath.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.org \
--cc=torvalds@linux-foundation.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