All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Bo Brantén" <bosse@acc.umu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86_64 ten times slower than i386
Date: Mon, 05 Nov 2007 11:11:19 -0800	[thread overview]
Message-ID: <472F6AD7.8050700@zytor.com> (raw)
In-Reply-To: <Pine.A41.4.64.0711051945280.708776@stalin.acc.umu.se>

Bo Brantén wrote:
> On Mon, 5 Nov 2007, H. Peter Anvin wrote:
> 
>>> reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
>>> reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
>>> reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1
>>> reg03: base=0xcf800000 (3320MB), size=   8MB: uncachable, count=1
>>> reg04: base=0xcf700000 (3319MB), size=   1MB: uncachable, count=1
>>> reg05: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
>>> reg06: base=0x120000000 (4608MB), size= 128MB: write-back, count=1
>>
>> What does your e820 map look like?
> 
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000008f000 (usable)
>  BIOS-e820: 000000000008f000 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 00000000cf561000 (usable)
>  BIOS-e820: 00000000cf561000 - 00000000cf56e000 (reserved)
>  BIOS-e820: 00000000cf56e000 - 00000000cf637000 (usable)
>  BIOS-e820: 00000000cf637000 - 00000000cf6e9000 (ACPI NVS)
>  BIOS-e820: 00000000cf6e9000 - 00000000cf6ed000 (usable)
>  BIOS-e820: 00000000cf6ed000 - 00000000cf6f2000 (ACPI data)
>  BIOS-e820: 00000000cf6f2000 - 00000000cf6f3000 (usable)
>  BIOS-e820: 00000000cf6f3000 - 00000000cf6ff000 (ACPI data)
>  BIOS-e820: 00000000cf6ff000 - 00000000cf700000 (usable)
>  BIOS-e820: 00000000cf700000 - 00000000d0000000 (reserved)
>  BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
>  BIOS-e820: 0000000100000000 - 000000012c000000 (usable)
> 

Okay, the bug is that the range 4736MB to 4800MB is marked USABLE in the 
map, but isn't covered by any MTRR.  Your BIOS is still buggy.

echo 'base=0x128000000 size=0x4000000 type=write-back' > /proc/mtrr

... should fix it since you still have an unused MTRR.  It might make X 
unhappy, though, since it may want an MTRR to mark the framebuffer 
write-combining.

	-hpa

  reply	other threads:[~2007-11-05 19:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 12:31 x86_64 ten times slower than i386 Bo Brantén
2007-11-03 16:26 ` Matt Mackall
2007-11-03 22:38   ` Bo Brantén
2007-11-03 22:54     ` Matt Mackall
2007-11-03 23:30     ` H. Peter Anvin
2007-11-05  8:06     ` Joseph Fannin
2007-11-05 10:15     ` Bo Brantén
2007-11-05 16:00       ` Bo Brantén
2007-11-05 17:23         ` H. Peter Anvin
2007-11-05 18:46           ` Bo Brantén
2007-11-05 19:11             ` H. Peter Anvin [this message]
     [not found]         ` <2c0942db0711050832t5207ea8bib1f75e59e071ade2@mail.gmail.com>
2007-11-06  0:26           ` Andi Kleen
2007-11-06  1:19             ` H. Peter Anvin
2007-11-06 19:40               ` Willy Tarreau
2007-11-06 19:50                 ` H. Peter Anvin
2007-11-06 19:53                   ` Willy Tarreau
2007-11-07 18:38             ` Jesse Barnes
2007-11-10 13:41         ` Bo Brantén
2007-11-05 17:22       ` H. Peter Anvin

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=472F6AD7.8050700@zytor.com \
    --to=hpa@zytor.com \
    --cc=bosse@acc.umu.se \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.