From: "H. Peter Anvin" <hpa@zytor.com>
To: Jordan Crouse <jordan.crouse@amd.com>
Cc: 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: Thu, 27 Sep 2007 16:36:28 -0700 [thread overview]
Message-ID: <46FC3E7C.7060600@zytor.com> (raw)
In-Reply-To: <20070927233408.GD4755@cosmic.amd.com>
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
Jordan Crouse wrote:
>>>
>> Oh bugger, looks like this one might be genuinely my fault after all.
>> The ID check in the new code is buggy.
>>
>> Can you please test this revised patch out (against current -git)?
>
>
> That looks the same as the previous patch you sent?
>
Sorry, this is the right one...
-hpa
[-- Attachment #2: smap.patch --]
[-- Type: text/x-patch, Size: 636 bytes --]
diff --git a/arch/i386/boot/memory.c b/arch/i386/boot/memory.c
index bccaa1c..2f37568 100644
--- a/arch/i386/boot/memory.c
+++ b/arch/i386/boot/memory.c
@@ -28,11 +28,10 @@ static int detect_memory_e820(void)
do {
size = sizeof(struct e820entry);
- id = SMAP;
asm("int $0x15; setc %0"
- : "=am" (err), "+b" (next), "+d" (id), "+c" (size),
+ : "=dm" (err), "+b" (next), "=a" (id), "+c" (size),
"=m" (*desc)
- : "D" (desc), "a" (0xe820));
+ : "D" (desc), "d" (SMAP), "a" (0xe820));
/* Some BIOSes stop returning SMAP in the middle of
the search loop. We don't know exactly how the BIOS
next prev parent reply other threads:[~2007-09-27 23:36 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 [this message]
2007-09-27 23:54 ` Jordan Crouse
2007-09-28 0:12 ` H. Peter Anvin
2007-09-28 13:05 ` Rafael J. Wysocki
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=46FC3E7C.7060600@zytor.com \
--to=hpa@zytor.com \
--cc=ak@suse.de \
--cc=cebbert@redhat.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