From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
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 17:46:24 -0700 [thread overview]
Message-ID: <48E80E60.8080106@zytor.com> (raw)
In-Reply-To: <1223157033-30217-2-git-send-email-yhlu.kernel@gmail.com>
Yinghai Lu wrote:
> + /*
> + * [0, 1M) should always be coverred by var mtrr with WB
> + * and fixed mtrrs should take effective before var mtrr for it
> + */
> + nr_range = add_range_with_merge(range, nr_range, 0,
> + (1ULL<<(20 - PAGE_SHIFT)) - 1);
> + /* sort the ranges */
> + sort(range, nr_range, sizeof(struct res_range), cmp_range, NULL);
> +
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.
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.
-hpa
next prev parent reply other threads:[~2008-10-05 0:46 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 [this message]
2008-10-05 1:49 ` Yinghai Lu
2008-10-05 1:52 ` H. Peter Anvin
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=48E80E60.8080106@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=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 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.