From: Toshi Kani <toshi.kani@hp.com>
To: hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com,
akpm@linux-foundation.org, arnd@arndb.de
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
jgross@suse.com, stefan.bader@canonical.com, luto@amacapital.net,
hmh@hmh.eng.br, yigal@plexistor.com, konrad.wilk@oracle.com,
Toshi Kani <toshi.kani@hp.com>
Subject: [PATCH v2 6/6] x86, pat: Update documentation for WT changes
Date: Wed, 10 Sep 2014 10:51:50 -0600 [thread overview]
Message-ID: <1410367910-6026-7-git-send-email-toshi.kani@hp.com> (raw)
In-Reply-To: <1410367910-6026-1-git-send-email-toshi.kani@hp.com>
This patch updates the PAT documentation file to cover the new
WT mapping interfaces.
Signed-off-by: Toshi Kani <toshi.kani@hp.com>
---
Documentation/x86/pat.txt | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/Documentation/x86/pat.txt b/Documentation/x86/pat.txt
index cf08c9f..445caab 100644
--- a/Documentation/x86/pat.txt
+++ b/Documentation/x86/pat.txt
@@ -12,7 +12,7 @@ virtual addresses.
PAT allows for different types of memory attributes. The most commonly used
ones that will be supported at this time are Write-back, Uncached,
-Write-combined and Uncached Minus.
+Write-combined, Write-through and Uncached Minus.
PAT APIs
@@ -38,12 +38,17 @@ ioremap_nocache | -- | UC- | UC- |
| | | |
ioremap_wc | -- | -- | WC |
| | | |
+ioremap_wt | -- | -- | WT |
+ | | | |
set_memory_uc | UC- | -- | -- |
set_memory_wb | | | |
| | | |
set_memory_wc | WC | -- | -- |
set_memory_wb | | | |
| | | |
+set_memory_wt | *1 | -- | WT |
+ set_memory_wb | | | |
+ | | | |
pci sysfs resource | -- | -- | UC- |
| | | |
pci sysfs resource_wc | -- | -- | WC |
@@ -79,6 +84,7 @@ pci proc | -- | -- | WC |
MTRR says !WB | | | |
| | | |
-------------------------------------------------------------------
+*1: -EINVAL due to the current limitation in reserve_memtype().
Advanced APIs for drivers
-------------------------
@@ -115,8 +121,8 @@ can be more restrictive, in case of any existing aliasing for that address.
For example: If there is an existing uncached mapping, a new ioremap_wc can
return uncached mapping in place of write-combine requested.
-set_memory_[uc|wc] and set_memory_wb should be used in pairs, where driver will
-first make a region uc or wc and switch it back to wb after use.
+set_memory_[uc|wc|wt] and set_memory_wb should be used in pairs, where driver
+will first make a region uc, wc or wt and switch it back to wb after use.
Over time writes to /proc/mtrr will be deprecated in favor of using PAT based
interfaces. Users writing to /proc/mtrr are suggested to use above interfaces.
@@ -126,6 +132,8 @@ types.
Drivers should use set_memory_[uc|wc] to set access type for RAM ranges.
+Drivers may map the entire NV-DIMM range with ioremap_cache and then change
+a specific range to wt with set_memory_wt.
PAT debugging
-------------
--
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-10 17:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 16:51 [PATCH v2 0/6] Support Write-Through mapping on x86 Toshi Kani
2014-09-10 16:51 ` [PATCH v2 1/6] x86, mm, pat: Set WT to PA4 slot of PAT MSR Toshi Kani
2014-09-12 19:33 ` Konrad Rzeszutek Wilk
2014-09-12 20:45 ` Toshi Kani
2014-09-10 16:51 ` [PATCH v2 2/6] x86, mm, pat: Change reserve_memtype() to handle WT Toshi Kani
2014-09-10 18:26 ` Andy Lutomirski
2014-09-10 19:14 ` H. Peter Anvin
2014-09-10 19:30 ` Toshi Kani
2014-09-10 20:14 ` H. Peter Anvin
2014-09-10 20:30 ` Toshi Kani
2014-09-10 21:06 ` Andy Lutomirski
2014-09-10 21:11 ` Toshi Kani
2014-09-10 21:27 ` Andy Lutomirski
2014-09-10 21:25 ` Toshi Kani
2014-09-10 21:39 ` H. Peter Anvin
2014-09-10 21:39 ` H. Peter Anvin
2014-09-10 21:47 ` Toshi Kani
2014-09-10 22:00 ` H. Peter Anvin
2014-09-10 23:24 ` Toshi Kani
2014-09-10 20:31 ` Andy Lutomirski
2014-09-12 19:41 ` Konrad Rzeszutek Wilk
2014-09-10 16:51 ` [PATCH v2 3/6] x86, mm, asm-gen: Add ioremap_wt() for WT Toshi Kani
2014-09-10 18:29 ` Andy Lutomirski
2014-09-10 19:40 ` Toshi Kani
2014-09-10 20:08 ` Andy Lutomirski
2014-09-12 19:42 ` Konrad Rzeszutek Wilk
2014-09-10 16:51 ` [PATCH v2 4/6] x86, mm: Add set_memory_wt() " Toshi Kani
2014-09-12 19:47 ` Konrad Rzeszutek Wilk
2014-09-10 16:51 ` [PATCH v2 5/6] x86, mm, pat: Add pgprot_writethrough() " Toshi Kani
2014-09-12 19:47 ` Konrad Rzeszutek Wilk
2014-09-10 16:51 ` Toshi Kani [this message]
2014-09-10 18:30 ` [PATCH v2 6/6] x86, pat: Update documentation for WT changes Andy Lutomirski
2014-09-10 20:12 ` Toshi Kani
2014-09-10 20:29 ` Andy Lutomirski
2014-09-10 21:34 ` Toshi Kani
2014-09-15 21:19 ` Toshi Kani
2014-09-16 1:22 ` Andy Lutomirski
2014-09-16 16:52 ` Toshi Kani
2014-09-16 21:45 ` Yigal Korman
2014-09-16 22:13 ` 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=1410367910-6026-7-git-send-email-toshi.kani@hp.com \
--to=toshi.kani@hp.com \
--cc=akpm@linux-foundation.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@redhat.com \
--cc=stefan.bader@canonical.com \
--cc=tglx@linutronix.de \
--cc=yigal@plexistor.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;
as well as URLs for NNTP newsgroup(s).