From: "Yinghai Lu" <yinghai@kernel.org>
To: "Dylan Taft" <d13f00l@gmail.com>, "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Andrew Morton" <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, "Yinghai Lu" <yhlu.kernel@gmail.com>
Subject: Re: [PATCH] x86: mtrr_cleanup hole size should be less than half of chunk_size v2
Date: Sat, 27 Sep 2008 22:58:16 -0700 [thread overview]
Message-ID: <86802c440809272258x1c418f0j7f274dfdfd8a87f6@mail.gmail.com> (raw)
In-Reply-To: <1222572366-24424-1-git-send-email-yhlu.kernel@gmail.com>
On Sat, Sep 27, 2008 at 8:26 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> v2: should check with half of range0 size instead of chunk_size
>
> So don't have silly big hole.
>
> in hpa's case we could auto detect instead of adding mtrr_chunk_size in command line
>
> Ingo, please consider to squash this one to previous one
> | commit 2313c2793d290a8cc37c428f8622c53f3fe1d6dc
> | Author: Yinghai Lu <yhlu.kernel@gmail.com>
> | Date: Sat Sep 27 00:30:08 2008 -0700
> |
> | x86: mtrr_cleanup optimization, v2
>
> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
>
Dylan,
please try tip/master after Ingo put this patch into it...
from
reg00: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1
reg01: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
reg02: base=0x120000000 (4608MB), size= 256MB: write-back, count=1
reg03: base=0xd0000000 (3328MB), size= 256MB: uncachable, count=1
reg04: base=0xe0000000 (3584MB), size= 512MB: uncachable, count=1
reg05: base=0xc7e00000 (3198MB), size= 2MB: uncachable, count=1
reg06: base=0xc8000000 (3200MB), size= 128MB: uncachable, count=1
you should get
Found optimal setting for mtrr clean up
gran_size: 1M chunk_size: 256M num_reg: 7 lose RAM: 0M
range0: 0000000000000000 - 00000000d0000000
Setting variable MTRR 0, base: 0MB, range: 2048MB, type WB
Setting variable MTRR 1, base: 2048MB, range: 1024MB, type WB
Setting variable MTRR 2, base: 3072MB, range: 256MB, type WB
hole: 00000000c7e00000 - 00000000d0000000
Setting variable MTRR 3, base: 3198MB, range: 2MB, type UC
Setting variable MTRR 4, base: 3200MB, range: 128MB, type UC
rangeX: 0000000100000000 - 0000000130000000
Setting variable MTRR 5, base: 4096MB, range: 512MB, type WB
Setting variable MTRR 6, base: 4608MB, range: 256MB, type WB
with mtrr_spare_reg_nr=2 you should get
Found optimal setting for mtrr clean up
gran_size: 1M chunk_size: 4M num_reg: 6 lose RAM: 0M
range0: 0000000000000000 - 00000000c8000000
Setting variable MTRR 0, base: 0MB, range: 2048MB, type WB
Setting variable MTRR 1, base: 2048MB, range: 1024MB, type WB
Setting variable MTRR 2, base: 3072MB, range: 128MB, type WB
hole: 00000000c7e00000 - 00000000c8000000
Setting variable MTRR 3, base: 3198MB, range: 2MB, type UC
rangeX: 0000000100000000 - 0000000130000000
Setting variable MTRR 4, base: 4096MB, range: 512MB, type WB
Setting variable MTRR 5, base: 4608MB, range: 256MB, type WB
next prev parent reply other threads:[~2008-09-28 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 3:26 Yinghai Lu
2008-09-28 5:58 ` Yinghai Lu [this message]
2008-09-28 7:13 ` Ingo Molnar
2008-09-28 9:10 ` 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=86802c440809272258x1c418f0j7f274dfdfd8a87f6@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=d13f00l@gmail.com \
--cc=hpa@zytor.com \
--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 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®