From: Toshi Kani <toshi.kani@hp.com>
To: hpa@zytor.com, tglx@linutronix.de, mingo@redhat.com,
akpm@linuxfoundation.org, arnd@arndb.de
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
jgross@suse.com, stefan.bader@canonical.com, luto@amacapital.net,
konrad.wilk@oracle.com, Toshi Kani <toshi.kani@hp.com>
Subject: [PATCH 2/5] x86, mm, pat: Change reserve_memtype() to handle WT
Date: Thu, 4 Sep 2014 12:35:36 -0600 [thread overview]
Message-ID: <1409855739-8985-3-git-send-email-toshi.kani@hp.com> (raw)
In-Reply-To: <1409855739-8985-1-git-send-email-toshi.kani@hp.com>
This patch changes reserve_memtype() to handle the WT cache mode.
When PAT is not enabled, it continues to set UC- to *new_type for
any non-WB request.
When a target range is RAM, reserve_ram_pages_type() fails for WT
for now. This function may not reserve a RAM range for WT since
reserve_ram_pages_type() uses the page flags limited to three memory
types, WB, WC and UC.
Signed-off-by: Toshi Kani <toshi.kani@hp.com>
---
arch/x86/include/asm/cacheflush.h | 4 ++++
arch/x86/mm/pat.c | 16 +++++++++++++---
2 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/arch/x86/include/asm/cacheflush.h b/arch/x86/include/asm/cacheflush.h
index 157644b..c912680 100644
--- a/arch/x86/include/asm/cacheflush.h
+++ b/arch/x86/include/asm/cacheflush.h
@@ -53,6 +53,10 @@ static inline void set_page_memtype(struct page *pg,
case _PAGE_CACHE_MODE_WB:
memtype_flags = _PGMT_WB;
break;
+ case _PAGE_CACHE_MODE_WT:
+ case _PAGE_CACHE_MODE_WP:
+ pr_err("set_page_memtype: unsupported cachemode %d\n", memtype);
+ BUG();
default:
memtype_flags = _PGMT_DEFAULT;
break;
diff --git a/arch/x86/mm/pat.c b/arch/x86/mm/pat.c
index b1891dc..87b21dd 100644
--- a/arch/x86/mm/pat.c
+++ b/arch/x86/mm/pat.c
@@ -271,6 +271,8 @@ static int pat_pagerange_is_ram(resource_size_t start, resource_size_t end)
/*
* For RAM pages, we use page flags to mark the pages with appropriate type.
+ * The page flags are currently limited to three types, WB, WC and UC. Hence,
+ * any request to WT or WP will fail with -EINVAL.
* Here we do two pass:
* - Find the memtype of all the pages in the range, look for any conflicts
* - In case of no conflicts, set the new memtype for pages in the range
@@ -282,6 +284,13 @@ static int reserve_ram_pages_type(u64 start, u64 end,
struct page *page;
u64 pfn;
+ if ((req_type == _PAGE_CACHE_MODE_WT) ||
+ (req_type == _PAGE_CACHE_MODE_WP)) {
+ if (new_type)
+ *new_type = _PAGE_CACHE_MODE_UC_MINUS;
+ return -EINVAL;
+ }
+
if (req_type == _PAGE_CACHE_MODE_UC) {
/* We do not support strong UC */
WARN_ON_ONCE(1);
@@ -331,6 +340,7 @@ static int free_ram_pages_type(u64 start, u64 end)
* - _PAGE_CACHE_MODE_WC
* - _PAGE_CACHE_MODE_UC_MINUS
* - _PAGE_CACHE_MODE_UC
+ * - _PAGE_CACHE_MODE_WT
*
* If new_type is NULL, function will return an error if it cannot reserve the
* region with req_type. If new_type is non-NULL, function will return
@@ -350,10 +360,10 @@ int reserve_memtype(u64 start, u64 end, enum page_cache_mode req_type,
if (!pat_enabled) {
/* This is identical to page table setting without PAT */
if (new_type) {
- if (req_type == _PAGE_CACHE_MODE_WC)
- *new_type = _PAGE_CACHE_MODE_UC_MINUS;
+ if (req_type == _PAGE_CACHE_MODE_WB)
+ *new_type = _PAGE_CACHE_MODE_WB;
else
- *new_type = req_type;
+ *new_type = _PAGE_CACHE_MODE_UC_MINUS;
}
return 0;
}
--
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-04 18:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 18:35 [PATCH 0/5] Support Write-Through mapping on x86 Toshi Kani
2014-09-04 18:35 ` [PATCH 1/5] x86, mm, pat: Set WT to PA4 slot of PAT MSR Toshi Kani
2014-09-04 20:11 ` Henrique de Moraes Holschuh
2014-09-04 20:21 ` H. Peter Anvin
2014-09-04 23:19 ` Henrique de Moraes Holschuh
2014-09-04 23:34 ` Andy Lutomirski
2014-09-05 0:29 ` Toshi Kani
2014-09-05 0:51 ` Andy Lutomirski
2014-09-05 14:00 ` Toshi Kani
2014-09-05 15:07 ` H. Peter Anvin
2014-09-05 15:22 ` Toshi Kani
2014-09-05 15:41 ` H. Peter Anvin
2014-09-05 15:42 ` Toshi Kani
2014-09-12 19:25 ` Konrad Rzeszutek Wilk
2014-09-12 20:03 ` Andy Lutomirski
2014-09-12 20:21 ` Konrad Rzeszutek Wilk
2014-09-04 20:31 ` Toshi Kani
2014-09-04 20:50 ` Andy Lutomirski
2014-09-04 23:27 ` Toshi Kani
2014-09-05 10:23 ` Ingo Molnar
2014-09-05 13:50 ` Toshi Kani
2014-09-07 13:58 ` Henrique de Moraes Holschuh
2014-09-04 18:35 ` Toshi Kani [this message]
2014-09-04 18:35 ` [PATCH 3/5] x86, mm, asm-gen: Add ioremap_wt() for WT Toshi Kani
2014-09-04 18:35 ` [PATCH 4/5] x86, mm: Add set_memory_wt() " Toshi Kani
2014-09-04 18:57 ` Andy Lutomirski
2014-09-04 18:57 ` Toshi Kani
2014-09-04 19:14 ` Andy Lutomirski
2014-09-04 19:30 ` Toshi Kani
2014-09-07 8:49 ` Yigal Korman
2014-09-07 16:49 ` Andy Lutomirski
2014-09-08 15:07 ` Toshi Kani
2014-09-08 17:23 ` Andy Lutomirski
2014-09-08 18:42 ` Toshi Kani
2014-09-04 18:35 ` [PATCH 5/5] x86, mm, pat: Add pgprot_writethrough() " 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=1409855739-8985-3-git-send-email-toshi.kani@hp.com \
--to=toshi.kani@hp.com \
--cc=akpm@linuxfoundation.org \
--cc=arnd@arndb.de \
--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 \
/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).