From: "H. Peter Anvin" <hpa@zytor.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Brice Goglin <brice.goglin@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org
Subject: Re: MTRR use in drivers
Date: Sun, 23 Jun 2013 17:31:23 -0700 [thread overview]
Message-ID: <43cfe710-f22c-4b0b-b7e0-a3c8e6a49096@email.android.com> (raw)
In-Reply-To: <20130624000224.GA2832@khazad-dum.debian.net>
The aliasing doesn't matter for Linux because we map the high and low half the same.
Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
>On Sun, 23 Jun 2013, H. Peter Anvin wrote:
>> On 06/23/2013 02:56 PM, Henrique de Moraes Holschuh wrote:
>> >
>> > And as far as I could find from Intel's not-that-complete public
>> > "specification updates", we are applying the errata workaround to a
>few more
>> > processors than strictly required, but since I have no idea how to
>write a
>> > test case, I can't whitelist the 3rd-gen Pentium M on my T43, nor
>can I get
>> > ThinkPad owners to test it for us on 1st and 2nd-gen Pentium M and
>report
>> > back.
>>
>> Which specific erratum are you referring to, here? The "WC becomes
>UC"
>> erratum? I don't think there is a sane testcase for it since it
>needs a
>> very complicated setup to trigger.
>
>There are at least two different nasty PAT issues that are not always
>critical, and one that outright hangs the processor (if the unsupported
>aliasing of WB with UC/WC happens).
>
>Interestingly enough, most of the P4-Xeons and P4 do not appear to have
>the
>"WC becomes UC" errata.
>
>However, LOTS of P4, M-P4, Xeon PIII, Xeon, and Pentium M have a bug
>where
>the four highest entries in the PAT table are inactive (aliased to the
>four
>lowest entries) in mode B (PSE) and mode C (PAE) for 4k pages. They
>work
>fine for large pages.
>
>Also, lots of them can hang if you ever alias WB with UC or WC (which
>is
>apparently an unsupported configuration anyway, or so it says in the
>errata).
>
>There are other weird aliasing nasties, such as one where you get
>memory
>corruption if you alias WB data with code (being accessed as UC or WC)
>in
>the same cacheline, and some stuff such as weirdness should the page
>table
>be on WC memory...
>
>I can track down most of the CPUIDs involved if you want, but someone
>from
>Intel would be better (I assume they actually have access to the errata
>documentation in some less idiotic way than reading a ton of badly
>indexed
>PDFs that take forever to find in their site).
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
prev parent reply other threads:[~2013-06-24 0:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 5:00 H. Peter Anvin
2013-06-23 6:35 ` Brice Goglin
2013-06-23 14:07 ` H. Peter Anvin
2013-06-23 19:29 ` Henrique de Moraes Holschuh
2013-06-23 20:02 ` H. Peter Anvin
2013-06-23 20:30 ` Dave Airlie
2013-06-23 20:38 ` H. Peter Anvin
2013-06-23 20:54 ` Dave Airlie
2013-06-23 20:58 ` H. Peter Anvin
2013-06-23 21:27 ` Dave Airlie
2013-06-23 23:09 ` Andy Lutomirski
2013-06-23 21:56 ` Henrique de Moraes Holschuh
2013-06-23 22:10 ` H. Peter Anvin
2013-06-24 0:02 ` Henrique de Moraes Holschuh
2013-06-24 0:31 ` H. Peter Anvin [this message]
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=43cfe710-f22c-4b0b-b7e0-a3c8e6a49096@email.android.com \
--to=hpa@zytor.com \
--cc=airlied@linux.ie \
--cc=brice.goglin@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®