From: Jeff Hartmann <jhartmann@valinux.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86 PAT errata
Date: Thu, 25 Jan 2001 17:35:53 -0700 [thread overview]
Message-ID: <3A70C669.4090800@valinux.com> (raw)
In-Reply-To: <200101251745.SAA07063@harpo.it.uu.se> <94q9ag$9bs$1@cesium.transmeta.com>
H. Peter Anvin wrote:
> Followup to: <200101251745.SAA07063@harpo.it.uu.se>
> By author: Mikael Pettersson <mikpe@csd.uu.se>
> In newsgroup: linux.dev.kernel
>
>> Before people get too exited about the x86 Page Attribute Table ...
>> Does Linux use mode B (CR4.PSE=1) or mode C (CR4.PAE=1) paging?
>> If so, known P6 errata must be taken into account.
>> In particular, Pentium III errata E27 and Pentium II errata A56
>> imply that only the low four PAT entries are working for 4KB
>> pages, if CR4.PSE or CR4.PAE is enabled.
>>
>
>
> All of the above. Sounds like PAT should be declared broken on these
> chips.
>
> -hpa
We can do set PAT entry one to be write combined. Currently it doesn't
look like anyone is using write through page mapping anywhere in the
kernel (Just PAGE_PWT set). Am I correct in that assumption?
-Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-26 0:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 17:45 x86 PAT errata Mikael Pettersson
2001-01-25 17:51 ` Jeff Hartmann
2001-01-25 22:28 ` H. Peter Anvin
2001-01-26 0:35 ` Jeff Hartmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-25 18:12 Mikael Pettersson
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=3A70C669.4090800@valinux.com \
--to=jhartmann@valinux.com \
--cc=hpa@zytor.com \
--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