From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jordan Crouse <jordan.crouse@amd.com>,
jkeating@redhat.com, Joerg Pommnitz <pommnitz@yahoo.com>,
Chuck Ebbert <cebbert@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@suse.de>
Subject: Re: More E820 brokenness
Date: Fri, 28 Sep 2007 15:05:01 +0200 [thread overview]
Message-ID: <200709281505.02542.rjw@sisk.pl> (raw)
In-Reply-To: <46FC46E3.5020508@zytor.com>
On Friday, 28 September 2007 02:12, H. Peter Anvin wrote:
> Jordan Crouse wrote:
> >
> > Worked, but that just raises more questions. Why didn't more x86 boxes
> > break or, alternatively, why did a new version of the BIOS fix the problem?
> > I guess we shouldn't look a gift horse in the mouth. Or something.
> >
>
> Why didn't more x86 boxes break... well, it's pretty natural an
> implementation of the BIOS to not clobber registers that aren't outputs.
> Arguably the BIOSes that do are still buggy, since there isn't a
> well-defined calling sequence for the BIOS and the convention that has
> evolved is "don't clobber anything unless it's an output."
>
> It's still wrong, however, especially since it means omitting the *real*
> SMAP check.
I'd like to update http://bugzilla.kernel.org/show_bug.cgi?id=9086 with correct
information.
Should I add a pointer to the patch from your previous message to it?
Greetings,
Rafael
prev parent reply other threads:[~2007-09-28 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 22:17 More E820 brokenness H. Peter Anvin
2007-09-27 22:33 ` Jordan Crouse
2007-09-27 22:47 ` H. Peter Anvin
2007-09-27 23:15 ` Jordan Crouse
2007-09-27 23:22 ` H. Peter Anvin
2007-09-27 23:27 ` H. Peter Anvin
2007-09-27 23:34 ` Jordan Crouse
2007-09-27 23:36 ` H. Peter Anvin
2007-09-27 23:54 ` Jordan Crouse
2007-09-28 0:12 ` H. Peter Anvin
2007-09-28 13:05 ` Rafael J. Wysocki [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=200709281505.02542.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ak@suse.de \
--cc=cebbert@redhat.com \
--cc=hpa@zytor.com \
--cc=jkeating@redhat.com \
--cc=jordan.crouse@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pommnitz@yahoo.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