mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yinghai@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.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, 4 Oct 2008 18:49:46 -0700	[thread overview]
Message-ID: <86802c440810041849g421ff524pf987f6c872e1d12a@mail.gmail.com> (raw)
In-Reply-To: <48E80E60.8080106@zytor.com>

On Sat, Oct 4, 2008 at 5:46 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> 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.

so it is safe to put it in WB, and can be spare some regs because it
start from base 0.

>
> 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..

YH

  reply	other threads:[~2008-10-05  1:49 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 [this message]
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=86802c440810041849g421ff524pf987f6c872e1d12a@mail.gmail.com \
    --to=yinghai@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®