public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Carlos R. Mafra" <crmafra2@gmail.com>
Cc: Alexander Lam <lambchop468@gmail.com>,
	linux-kernel@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>
Subject: Re: mtrr cleanup not doing anything on 2.6.33-rc7
Date: Thu, 11 Feb 2010 06:56:59 -0800	[thread overview]
Message-ID: <4B741ABB.2000600@zytor.com> (raw)
In-Reply-To: <20100211101013.GA4892@Pilar.aei.mpg.de>

On 02/11/2010 02:10 AM, Carlos R. Mafra wrote:
> [Add people in that commit to Cc: list, just in case]
> 
> On Mi 10.Feb'10 at 20:48:49 -0500, Alexander Lam wrote:
>> On Wed, Feb 10, 2010 at 3:02 PM, Alexander Lam <lambchop468@gmail.com> wrote:
>>>
>>> My kernel config has the following:
>>> CONFIG_MTRR=y
>>> CONFIG_MTRR_SANITIZER=y
>>> CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
>>> CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
>>>
>>> With previous kernels, dmesg would show that the sanitizer was indeed
>>> cleaning up the mtrrs [1]
>>>
>>> but now, with 2.6.33-rc7 there is no indication that this is occuring,
>>
>> For those who run across this later,
>>
>> Found out that commit 508d85c2c6bc8cba53d2a54d9a306ad64a0a80bf,
>>    x86: When cleaning MTRRs, do not fold WP into UC
>>
>> causes mtrr cleanup not to run on my machine.
>>
>> Probably not worth fixing because the i915 error message is harmless.
>> --

You're not stating what your MTRR setup looks like, and hence if there
is anything to clean up.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2010-02-11 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 20:02 mtrr cleanup not doing anything on 2.6.33-rc7 Alexander Lam
2010-02-11  1:48 ` Alexander Lam
2010-02-11 10:10   ` Carlos R. Mafra
2010-02-11 14:56     ` H. Peter Anvin [this message]
2010-02-11 17:15       ` Carlos R. Mafra

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=4B741ABB.2000600@zytor.com \
    --to=hpa@zytor.com \
    --cc=crmafra2@gmail.com \
    --cc=lambchop468@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox