From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@au1.ibm.com>
Cc: linuxppc-dev list <Linuxppc-dev@ozlabs.org>
Subject: [patch 5/5] powerpc: Dont clear _PAGE_COHERENT when _PAGE_SAO is set
Date: Mon, 07 Jul 2008 09:28:55 -0500 [thread overview]
Message-ID: <20080707143011.729373219@linux.vnet.ibm.com> (raw)
In-Reply-To: 20080707142850.034542257@linux.vnet.ibm.com
Signed-off-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
arch/powerpc/platforms/pseries/lpar.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: b/arch/powerpc/platforms/pseries/lpar.c
===================================================================
--- a/arch/powerpc/platforms/pseries/lpar.c
+++ b/arch/powerpc/platforms/pseries/lpar.c
@@ -305,7 +305,8 @@
flags = 0;
/* Make pHyp happy */
- if (rflags & (_PAGE_GUARDED|_PAGE_NO_CACHE))
+ if ((rflags & _PAGE_GUARDED) ||
+ ((rflags & _PAGE_NO_CACHE) & !(rflags & _PAGE_WRITETHRU)))
hpte_r &= ~_PAGE_COHERENT;
lpar_rc = plpar_pte_enter(flags, hpte_group, hpte_v, hpte_r, &slot);
--
Dave Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2008-07-07 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 14:28 [patch 0/5] Strong Access Ordering Dave Kleikamp
2008-07-07 14:28 ` [patch 1/5] mm: Allow architectures to define additional protection bits Dave Kleikamp
2008-07-07 14:28 ` [patch 2/5] powerpc: Define flags for Strong Access Ordering Dave Kleikamp
2008-07-07 14:28 ` [patch 3/5] powerpc: Add SAO Feature bit to the cputable Dave Kleikamp
2008-07-07 14:28 ` [patch 4/5] powerpc: Add Strong Access Ordering Dave Kleikamp
2008-07-07 14:28 ` Dave Kleikamp [this message]
2008-07-09 3:46 ` [patch 5/5] powerpc: Dont clear _PAGE_COHERENT when _PAGE_SAO is set Benjamin Herrenschmidt
2008-07-09 15:28 ` Dave Kleikamp
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=20080707143011.729373219@linux.vnet.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=benh@au1.ibm.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).