From: Toshi Kani <toshi.kani@hp.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com,
akpm@linuxfoundation.org, arnd@arndb.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, jgross@suse.com,
stefan.bader@canonical.com, luto@amacapital.net,
konrad.wilk@oracle.com
Subject: Re: [PATCH 1/5] x86, mm, pat: Set WT to PA4 slot of PAT MSR
Date: Fri, 05 Sep 2014 07:50:23 -0600 [thread overview]
Message-ID: <1409925023.28990.176.camel@misato.fc.hp.com> (raw)
In-Reply-To: <20140905102347.GA30096@gmail.com>
On Fri, 2014-09-05 at 12:23 +0200, Ingo Molnar wrote:
> * Toshi Kani <toshi.kani@hp.com> wrote:
>
> > On Thu, 2014-09-04 at 14:31 -0600, Toshi Kani wrote:
> > > On Thu, 2014-09-04 at 17:11 -0300, Henrique de Moraes Holschuh wrote:
> > > > On Thu, 04 Sep 2014, Toshi Kani wrote:
> > > > > This patch sets WT to the PA4 slot in the PAT MSR when the processor
> > > > > is not affected by the PAT errata. The upper 4 slots of the PAT MSR
> > > > > are continued to be unused on the following Intel processors.
> > > > >
> > > > > errata cpuid
> > > > > --------------------------------------
> > > > > Pentium 2, A52 family 0x6, model 0x5
> > > > > Pentium 3, E27 family 0x6, model 0x7
> > > > > Pentium M, Y26 family 0x6, model 0x9
> > > > > Pentium 4, N46 family 0xf, model 0x0
> > > > >
> > > > > For these affected processors, _PAGE_CACHE_MODE_WT is redirected to UC-
> > > > > per the default setup in __cachemode2pte_tbl[].
> > > >
> > > > There are at least two PAT errata. The blacklist is in
> > > > arch/x86/kernel/cpu/intel.c:
> > > >
> > > > if (c->x86 == 6 && c->x86_model < 15)
> > > > clear_cpu_cap(c, X86_FEATURE_PAT);
> > > >
> > > > It covers model 13, which is not in your blacklist.
> > > >
> > > > It *is* possible that PAT would work on model 13, as I don't think it has
> > > > any PAT errata listed and it was blacklisted "just in case" (from memory. I
> > > > did not re-check), but this is untested, and unwise to enable on an aging
> > > > platform.
> > > >
> > > > I am worried of uncharted territory, here. I'd actually advocate for not
> > > > enabling the upper four PAT entries on IA-32 at all, unless Windows 9X / XP
> > > > is using them as well. Is this a real concern, or am I being overly
> > > > cautious?
> > >
> > > The blacklist you pointed out covers a different PAT errata, and is
> > > still effective after this change. pat_init() will call pat_disable()
> > > and the PAT will continue to be disabled on these processors. There is
> > > no change for them.
> > >
> > > My blacklist covers the PAT errata that makes the upper four bit
> > > unusable when the PAT is enabled.
> >
> > I checked more carefully, and it turns out that the processors
> > that have the WC bug with PAT/MTRR also have the upper four bit
> > bug in PAT as well. The updated blacklist is:
> >
> > errata cpuid
> > --------------------------------------
> > Pentium 2, A52 family 0x6, model 0x5
> > Pentium 3, E27 family 0x6, model 0x7, 0x8
> > Pentium 3 Xeon, G26 family 0x6, model 0x7, 0x8, 0xa
> > Pentium M, Y26 family 0x6, model 0x9
> > Pentium M 90nm, X9 family 0x6, model 0xd
> > Pentium 4, N46 family 0xf, model 0x0
> >
> > So, the check can be the same as cpu/intel.c, except that early
> > Pentium 4 steppings also have the upper four bit bug. I will
> > update the check. In any case, this check is only meaningful
> > for P4 since the PAT is disabled for P2/3/M.
>
> Any reason why we have to create such a sharp boundary, instead
> of simply saying: 'disable PAT on all x86 CPU families that have
> at least one buggy model'?
>
> That would nicely sort out all the broken CPUs, and would make it
> highly unlikely that we'd accidentally forget about a model or
> two.
Agreed. I will disable this feature on all Pentium 4 models as well. I
do not think there is any necessity to enable it on Pentium 4.
Thanks,
-Toshi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-09-05 14:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 18:35 [PATCH 0/5] Support Write-Through mapping on x86 Toshi Kani
2014-09-04 18:35 ` [PATCH 1/5] x86, mm, pat: Set WT to PA4 slot of PAT MSR Toshi Kani
2014-09-04 20:11 ` Henrique de Moraes Holschuh
2014-09-04 20:21 ` H. Peter Anvin
2014-09-04 23:19 ` Henrique de Moraes Holschuh
2014-09-04 23:34 ` Andy Lutomirski
2014-09-05 0:29 ` Toshi Kani
2014-09-05 0:51 ` Andy Lutomirski
2014-09-05 14:00 ` Toshi Kani
2014-09-05 15:07 ` H. Peter Anvin
2014-09-05 15:22 ` Toshi Kani
2014-09-05 15:41 ` H. Peter Anvin
2014-09-05 15:42 ` Toshi Kani
2014-09-12 19:25 ` Konrad Rzeszutek Wilk
2014-09-12 20:03 ` Andy Lutomirski
2014-09-12 20:21 ` Konrad Rzeszutek Wilk
2014-09-04 20:31 ` Toshi Kani
2014-09-04 20:50 ` Andy Lutomirski
2014-09-04 23:27 ` Toshi Kani
2014-09-05 10:23 ` Ingo Molnar
2014-09-05 13:50 ` Toshi Kani [this message]
2014-09-07 13:58 ` Henrique de Moraes Holschuh
2014-09-04 18:35 ` [PATCH 2/5] x86, mm, pat: Change reserve_memtype() to handle WT Toshi Kani
2014-09-04 18:35 ` [PATCH 3/5] x86, mm, asm-gen: Add ioremap_wt() for WT Toshi Kani
2014-09-04 18:35 ` [PATCH 4/5] x86, mm: Add set_memory_wt() " Toshi Kani
2014-09-04 18:57 ` Andy Lutomirski
2014-09-04 18:57 ` Toshi Kani
2014-09-04 19:14 ` Andy Lutomirski
2014-09-04 19:30 ` Toshi Kani
2014-09-07 8:49 ` Yigal Korman
2014-09-07 16:49 ` Andy Lutomirski
2014-09-08 15:07 ` Toshi Kani
2014-09-08 17:23 ` Andy Lutomirski
2014-09-08 18:42 ` Toshi Kani
2014-09-04 18:35 ` [PATCH 5/5] x86, mm, pat: Add pgprot_writethrough() " Toshi Kani
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=1409925023.28990.176.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=akpm@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=stefan.bader@canonical.com \
--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