From: Andi Kleen <andi@firstfloor.org>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: Zhao Forrest <forrest.zhao@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
discuss@x86-64.org, linux-kernel@vger.kernel.org,
yhlu.kernel@gmail.com, mingo@elte.hu, ak@suse.de
Subject: Re: Does Linux have plan to support memory hole remapping?
Date: Wed, 9 Apr 2008 10:49:09 +0200 [thread overview]
Message-ID: <20080409084909.GE19010@one.firstfloor.org> (raw)
In-Reply-To: <20080409083700.GU3700@mea-ext.zmailer.org>
> I second that. On my home machine I have early ASUS AMD x64 board from
> a few years ago. For it I did buy CPU with this memory mapping hardware
> inside, but the BIOS did not support it correctly until a year or two latter,
> thus I was not able to use all of 4 GB of memory I had installed there.
To be fair the low-end boards often state in their documentation that they only
got tested with upto 2GB. So strictly you were out of spec if you plug in 4GB.
> Looks like BIOS-writers don't really have test environments for extreme
> far edges of system configurations - "yes, we support --> sales $$$".
> And once product ships, rare extreme users rarely report anything back.
It depends on how much you pay. Higher end boards tend to get tested
in higher end configurations. Low end boards not.
-Andi
next prev parent reply other threads:[~2008-04-09 8:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 7:54 Does Linux have plan to support memory hole remapping? Zhao Forrest
2008-04-09 8:01 ` Andi Kleen
2008-04-09 8:37 ` Matti Aarnio
2008-04-09 8:49 ` Andi Kleen [this message]
2008-04-09 8:54 ` Ingo Molnar
2008-04-09 9:03 ` Andi Kleen
2008-04-10 0:34 ` Kasper Sandberg
2008-04-10 2:09 ` H. Peter Anvin
2008-04-10 12:41 ` Kasper Sandberg
2008-04-10 6:51 ` Andi Kleen
2008-04-09 9:04 ` Zhao Forrest
2008-04-09 9:13 ` Andi Kleen
2008-04-10 6:51 ` Zhao Forrest
2008-04-10 7:22 ` Andi Kleen
2008-04-09 9:50 ` Arne Georg Gleditsch
2008-04-09 10:03 ` Andi Kleen
2008-04-09 10:16 ` Arne Georg Gleditsch
2008-04-09 18:02 ` Yinghai Lu
2008-04-09 13:34 ` Lennart Sorensen
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=20080409084909.GE19010@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=forrest.zhao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=mingo@elte.hu \
--cc=yhlu.kernel@gmail.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