From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] x86: mtrr_cleanup: first 1M should be coverred in var mtrrs
Date: Sat, 04 Oct 2008 18:52:45 -0700 [thread overview]
Message-ID: <48E81DED.7050902@zytor.com> (raw)
In-Reply-To: <86802c440810041849g421ff524pf987f6c872e1d12a@mail.gmail.com>
Yinghai Lu wrote:
>> The first 1 MB is a total don't care for the variable MTRRs -- they don't
>> have to be covered *or* uncovered, since the entire first 1 MB is addressed
>> by fixed MTRRs.
>
> so it is safe to put it in WB, and can be spare some regs because it
> start from base 0.
Yes, my point was that you can make those whatever you want. It doesn't
have to be WB; it can be any value.
>> In practice, it is *likely* that you're going to want to merge it with a WB
>> MTRR, but with various vendors doing all kinds of strange things on
>> EFI-damaged platforms, it may not always be that way.
>
> EFI will not use fixed-mtrr for first 1M? and not cover first 1M in
> var mtrr with WB? that will run out mtrr regs..
There are some systems which, apparently, don't have RAM there. Don't
ask me how or why.
-hpa
next prev parent reply other threads:[~2008-10-05 1:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 21:50 [PATCH 1/3] x86: mtrr_cleanup: print out correct type Yinghai Lu
2008-10-04 21:50 ` [PATCH 2/3] x86: mtrr_cleanup: first 1M should be coverred in var mtrrs Yinghai Lu
2008-10-05 0:46 ` H. Peter Anvin
2008-10-05 1:49 ` Yinghai Lu
2008-10-05 1:52 ` H. Peter Anvin [this message]
2008-10-05 1:59 ` Yinghai Lu
2008-10-05 2:04 ` H. Peter Anvin
2008-10-04 21:50 ` [PATCH 3/3] x86: mtrr_cleanup: treat WRPROT as UNCACHEABLE Yinghai Lu
2008-10-05 0:42 ` [PATCH 1/3] x86: mtrr_cleanup: print out correct type H. Peter Anvin
2008-10-05 1:42 ` Yinghai Lu
2008-10-05 3:10 ` 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=48E81DED.7050902@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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