From: Ingo Molnar <mingo@elte.hu>
To: Meelis Roos <mroos@linux.ee>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Yinghai Lu <yinghai@kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: strange MTRR on 2.6.29-git
Date: Sun, 5 Apr 2009 15:41:09 +0200 [thread overview]
Message-ID: <20090405134109.GA24782@elte.hu> (raw)
In-Reply-To: <Pine.SOC.4.64.0904050953480.2958@math.ut.ee>
* Meelis Roos <mroos@linux.ee> wrote:
> > > reg00: base=0x000000000 ( 0MB), size= 512MB, count=1: write-back
> > > reg01: base=0x020000000 ( 512MB), size= 1MB, count=1: write-back
> > > reg02: base=0x020000000 ( 512MB), size= 1MB, count=1: uncachable
> > > reg03: base=0x0f2000000 ( 3872MB), size= 32MB, count=2: write-combining
> > > reg04: base=0x0f8000000 ( 3968MB), size= 64MB, count=1: write-combining
>
> > that is original setting by BIOS.
> > it should be ok.
> > if you like, could try to enable
> >
> > CONFIG_MTRR=y
> > CONFIG_MTRR_SANITIZER=y
> > CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
> > CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
> >
> > it could do the clean up for you.
>
> Thank you, it did clean it up:
>
> reg00: base=0x000000000 ( 0MB), size= 512MB, count=1: write-back
> reg01: base=0x0f2000000 ( 3872MB), size= 32MB, count=2: write-combining
> reg02: base=0x0f8000000 ( 3968MB), size= 64MB, count=1: write-combining
>
> and it removed the overlapping MTRR-s altogether since there was
> no RAM described t be here. Seems to work fine.
ok, great.
I'm wondering whether CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT should be
1 by default in the future.
Ingo
next prev parent reply other threads:[~2009-04-05 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 14:13 strange MTRR on 2.6.29-git Meelis Roos
2009-04-01 14:25 ` Meelis Roos
2009-04-01 18:43 ` Yinghai Lu
2009-04-05 7:12 ` Meelis Roos
2009-04-05 13:41 ` Ingo Molnar [this message]
2009-04-05 20:05 ` 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=20090405134109.GA24782@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--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 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.