From: David Wragg <dpw@doc.ic.ac.uk>
To: Timur Tabi <ttabi@interactivesi.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: ioremap_nocache problem?
Date: 24 Jan 2001 15:39:10 +0000 [thread overview]
Message-ID: <y7rk87lnen5.fsf@sytry.doc.ic.ac.uk> (raw)
In-Reply-To: Timur Tabi's message of "Wed, 24 Jan 2001 09:14:02 -0600"
Timur Tabi <ttabi@interactivesi.com> writes:
> ** Reply to message from David Wragg <dpw@doc.ic.ac.uk> on 24 Jan 2001
> 00:50:20 +0000
> > (x86 processors with PAT and IA64 can set write-combining through
> >page flags. x86 processors with MTRRs but not PAT would need a more
> >elaborate implementation for write-combining.)
>
> What is PAT? I desperately need to figure out how to turn on write
> combining on a per-page level. I thought I had to use MTRRs, but now
> you're saying I can use this "PAT" thing instead. Please explain!
PAT is basically the MTRR memory types on a per-page basis. It adds a
new flag bit to the x86 page table entry, then that bit together with
the PCD and PWT bits is used to do a look-up in an 8-entry table that
gives the effective memory type (the table is set through an MSR).
All the details are in the Intel x86 manual, volume 3
<URL:http://developer.intel.com/design/pentium4/manuals/> (at the end
of chapter 9).
Quite a lot of the x86 CPUs out there support PAT: The PII except the
first couple of models, the Celeron except the first model, the PIII,
all PII and PIII Xeons, the P4, all AMD K7 models. I'm guessing, but
I suspect that the majority of x86 CPUs supporting write combining in
any form that have been made also support PAT.
I wish Intel had put PAT in the PPro, rather than messing everyone
around with MTRRs (MTRRs are good for BIOS writers, but a pain for
everyone else).
David Wragg
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-01-24 15:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 10:30 Mark Mokryn
2001-01-23 16:53 ` Timur Tabi
2001-01-25 15:16 ` Stephen C. Tweedie
2001-01-25 15:56 ` Timur Tabi
2001-01-25 16:44 ` Roman Zippel
2001-01-25 16:49 ` Timur Tabi
2001-01-26 10:39 ` Stephen C. Tweedie
[not found] ` <20010125165001Z132264-460+11@vger.kernel.org>
2001-01-25 17:04 ` Jeff Hartmann
2001-01-25 17:11 ` Timur Tabi
[not found] ` <E14LpvQ-0008Pw-00@mail.valinux.com>
2001-01-25 17:47 ` Jeff Hartmann
2001-01-25 17:53 ` Timur Tabi
2001-01-26 10:43 ` Stephen C. Tweedie
2001-01-26 16:32 ` Eric W. Biederman
2001-01-26 19:22 ` Timur Tabi
[not found] ` <20010125175308Z130507-460+45@vger.kernel.org>
2001-01-25 18:13 ` Jeff Hartmann
2001-01-25 18:18 ` Timur Tabi
[not found] ` <E14Lqyt-0003z6-00@mail.valinux.com>
2001-01-25 18:46 ` Jeff Hartmann
[not found] ` <200101251556.f0PFuPd01743@mail.redhat.com>
2001-01-26 10:37 ` Stephen C. Tweedie
2001-01-23 18:12 ` Roman Zippel
2001-01-23 18:38 ` Timur Tabi
2001-01-24 0:50 ` David Wragg, David Wragg
2001-01-24 15:14 ` Timur Tabi
[not found] ` <E14LRce-0008FU-00@diver.doc.ic.ac.uk>
2001-01-24 15:39 ` David Wragg [this message]
[not found] ` <20010123183847Z131216-18594+636@vger.kernel.org>
2001-01-24 1:01 ` David Wragg
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=y7rk87lnen5.fsf@sytry.doc.ic.ac.uk \
--to=dpw@doc.ic.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ttabi@interactivesi.com \
/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