From: Andi Kleen <andi@firstfloor.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Andi Kleen <andi@firstfloor.org>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org
Subject: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
Date: Fri, 1 Jun 2007 23:19:43 +0200 [thread overview]
Message-ID: <20070601211943.GO7217@one.firstfloor.org> (raw)
In-Reply-To: <200706011407.51779.jbarnes@virtuousgeek.org>
On Fri, Jun 01, 2007 at 02:07:51PM -0700, Jesse Barnes wrote:
> On Friday, June 1, 2007 2:14:17 Andi Kleen wrote:
> > Jesse Barnes <jbarnes@virtuousgeek.org> writes:
> > > (or we get proper PAT support, which I think would make this problem
> > > go away as well).
> >
> > No it won't. If the basic MTRRs for memory are wrong just having PAT
> > support in drivers (which already exist in a limited form already, just for
> > UC only) won't change anything.
>
> No obviously just using PAT for drivers wouldn't help, I was thinking more of
> having one PAT type be WB memory, and using it by default for most PTEs
Then the BIOS couldn't override it anymore in case it is needed somewhere.
e.g. normally we just use normal 2MB direct mappings for the hole
if there is memory beyond it and the hole doesn't need to be 2MB aligned.
Just assuming UC for all reserved pages would be also pretty drastic
and likely result in many 2MB pages being split and using a lot more
TLB.
> covering normal memory. If that's not possible, then it seems sensible to
And normally the MTRRs win, don't they (if I remember the table correctly)
So if the MTRR says UC and PAT disagrees it might not actually help
-Andi
next prev parent reply other threads:[~2007-06-01 21:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 18:14 Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately? Justin Piszcz
2007-06-01 19:10 ` Jesse Barnes
2007-06-01 19:17 ` Justin Piszcz
2007-06-01 19:19 ` Justin Piszcz
2007-06-01 19:21 ` Jesse Barnes
2007-06-01 21:14 ` Andi Kleen
2007-06-01 20:19 ` Justin Piszcz
2007-06-01 20:24 ` Andi Kleen
2007-06-01 20:26 ` Justin Piszcz
2007-06-01 21:07 ` Jesse Barnes
2007-06-01 21:19 ` Andi Kleen [this message]
2007-06-01 21:35 ` Jesse Barnes
2007-06-01 21:41 ` Jesse Barnes
2007-06-02 1:05 ` Venki Pallipadi
2007-06-02 1:15 ` Jesse Barnes
2007-06-02 8:43 ` Justin Piszcz
2007-06-02 9:22 ` Andi Kleen
2007-06-02 20:11 ` Justin Piszcz
2007-06-03 9:15 ` Matt Keenan
2007-06-04 15:40 ` Jesse Barnes
2007-06-04 15:48 ` Ray Lee
2007-06-04 15:49 ` Justin Piszcz
2007-06-04 16:01 ` Ray Lee
2007-06-04 15:54 ` Jesse Barnes
2007-06-04 18:24 ` Andi Kleen
2007-06-04 18:13 ` Eric W. Biederman
2007-06-04 18:22 ` Justin Piszcz
2007-06-04 19:08 ` Justin Piszcz
2007-06-04 19:17 ` Jesse Barnes
2007-06-04 19:18 ` Alan Cox
2007-06-04 21:01 ` Eric W. Biederman
2007-06-05 0:59 ` Yinghai Lu
2007-06-05 1:38 ` Eric W. Biederman
2007-06-05 9:46 ` Andi Kleen
2007-06-05 13:18 ` Justin Piszcz
2007-06-05 17:20 ` Jesse Barnes
2007-06-07 8:47 ` Andi Kleen
2007-06-04 19:23 ` Andi Kleen
2007-06-04 19:24 ` Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately? II Andi Kleen
2007-06-05 0:54 ` Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately? Yinghai Lu
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=20070601211943.GO7217@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jpiszcz@lucidpixels.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox