From: "zhenzhong.duan" <zhenzhong.duan@oracle.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Peter Hurley <peter@hurleysoftware.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] x86: mtrr: Constrain WB MTRR to max phys mem prior to cleanup
Date: Mon, 10 Sep 2012 11:54:56 +0800 [thread overview]
Message-ID: <504D6490.2060606@oracle.com> (raw)
In-Reply-To: <504A3FA9.1050502@zytor.com>
于 2012-09-08 02:40, H. Peter Anvin 写道:
> On 09/07/2012 10:44 AM, Peter Hurley wrote:
> \>
>> diff --git a/arch/x86/kernel/cpu/mtrr/cleanup.c
>> b/arch/x86/kernel/cpu/mtrr/cleanup.c
>
> I really don't like it as it introduces yet another user of max_pfn,
> which should be going away. Furthermore, the better question is what
> remaining needs there are for MTRR cleanup; historically the reason
> was that it prevented the display from being mapped WC via MTRR due to
> the MTRR conflict resolution rules favoring UC.
For a large memory system, mtrr_cleanup offten fail in most case. Even
if it succeed, it often occupy all of MTRR entrys.
How was display mapped as WC in above case?
Why did bios give a lot of space then real mem, for hotplug?
>
> However, the right way to fix that is to use the PAT interfaces, which
> doesn't have this drawback -- then MTRR cleanup becomes entirely
> superfluous and the problem goes away.
Do you mean disable MTRR totally here?
Regards
zduan
next prev parent reply other threads:[~2012-09-10 3:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 17:44 Peter Hurley
2012-09-07 18:40 ` H. Peter Anvin
2012-09-10 3:54 ` zhenzhong.duan [this message]
2012-09-28 17:37 ` Peter Hurley
2012-09-29 2:41 ` Zhenzhong Duan
2012-09-29 3:16 ` H. Peter Anvin
2012-09-29 10:46 ` Henrique de Moraes Holschuh
2012-09-29 15:05 ` H. Peter Anvin
2012-09-29 20:11 ` Henrique de Moraes Holschuh
2012-09-29 20:16 ` H. Peter Anvin
2012-09-29 20:17 ` H. Peter Anvin
2012-09-29 21:25 ` Henrique de Moraes Holschuh
-- strict thread matches above, loose matches on Subject: below --
2012-07-24 20:51 Peter Hurley
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=504D6490.2060606@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peter@hurleysoftware.com \
--cc=tglx@linutronix.de \
--cc=x86@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
Powered by JetHome