[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140904231923.GA15320@khazad-dum.debian.net>
Date: Thu, 4 Sep 2014 20:19:23 -0300
From: Henrique de Moraes Holschuh <hmh@....eng.br>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Toshi Kani <toshi.kani@...com>, tglx@...utronix.de,
mingo@...hat.com, akpm@...uxfoundation.org, arnd@...db.de,
linux-mm@...ck.org, linux-kernel@...r.kernel.org, jgross@...e.com,
stefan.bader@...onical.com, luto@...capital.net,
konrad.wilk@...cle.com
Subject: Re: [PATCH 1/5] x86, mm, pat: Set WT to PA4 slot of PAT MSR
On Thu, 04 Sep 2014, H. Peter Anvin wrote:
> On 09/04/2014 01:11 PM, Henrique de Moraes Holschuh wrote:
> > 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?
>
> It is extremely unlikely that we'd have PAT issues in 32-bit mode and
> not in 64-bit mode on the same CPU.
Sure, but is it really a good idea to enable this on the *old* non-64-bit
capable processors (note: I don't mean x86-64 processors operating in 32-bit
mode) ?
> As far as I know, the current blacklist rule is very conservative due to
> lack of testing more than anything else.
I was told that much in 2009 when I asked why cpuid 0x6d8 was blacklisted
from using PAT :-)
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists