linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: paulus@samba.org, thuth@redhat.com, jstancek@redhat.com,
	dgibson@redhat.com, benh@kernel.crashing.org,
	Stewart Smith <stewart@linux.vnet.ibm.com>,
	stable@vger.kernel.org
Subject: [PATCH] PPC: fix LOGMPP instruction opcode and inline asm
Date: Fri, 16 Oct 2015 12:20:35 +1100	[thread overview]
Message-ID: <1444958435-18808-1-git-send-email-stewart@linux.vnet.ibm.com> (raw)

Back in 9678cda when we started using the Micro Partition Prefetch Engine
in POWER8 for KVM, there were two mistakes introduced from the original
patch used for investigation and microbenchmarks.

One mistake was that the opcode was constructed incorrectly, putting
the register in the wrong field in the opcode, meaning that we were
asking the chip to read the memory address from some other register than
what we intended - probably r0. For those unfortunate enough to have r0
point somewhere in memory they cared about, the prefetch engine would
gleefully trash all over it leading to some data you cared about being
replaced with a list of physical addresses.

In addition, the logmpp inline function incorrectly used R1 rather than
%0, leading to even if we got the construction of the instruction right,
we'd still generate the wrong thing, looking at the address in r1 rather
than whatever we were asked to look at.

So, this patch fixes the following:
- the inline logmpp function's inline asm to be correct
- puts the register in the right field of the instruction

This bug would overwrite a single 64k page.

https://bugzilla.redhat.com/show_bug.cgi?id=1269653
https://bugzilla.redhat.com/show_bug.cgi?id=1271997

Cc: stable@vger.kernel.org
Fixes: 9678cda ("Use the POWER8 Micro Partition Prefetch Engine in KVM HV")
Reported-by: David Gibson <david@gibson.dropbear.id.au>
Reported-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Suggested-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Suggested-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
---
 arch/powerpc/include/asm/cache.h      | 2 +-
 arch/powerpc/include/asm/ppc-opcode.h | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/powerpc/include/asm/cache.h b/arch/powerpc/include/asm/cache.h
index 34a05a1a990b..3af1c1e35435 100644
--- a/arch/powerpc/include/asm/cache.h
+++ b/arch/powerpc/include/asm/cache.h
@@ -43,7 +43,7 @@ extern struct ppc64_caches ppc64_caches;
 
 static inline void logmpp(u64 x)
 {
-	asm volatile(PPC_LOGMPP(R1) : : "r" (x));
+	asm volatile(PPC_LOGMPP(%0) : : "r" (x));
 }
 
 #endif /* __powerpc64__ && ! __ASSEMBLY__ */
diff --git a/arch/powerpc/include/asm/ppc-opcode.h b/arch/powerpc/include/asm/ppc-opcode.h
index 65136928a572..0dc2f6f9b445 100644
--- a/arch/powerpc/include/asm/ppc-opcode.h
+++ b/arch/powerpc/include/asm/ppc-opcode.h
@@ -304,8 +304,8 @@
 #define PPC_LDARX(t, a, b, eh)	stringify_in_c(.long PPC_INST_LDARX | \
 					___PPC_RT(t) | ___PPC_RA(a) | \
 					___PPC_RB(b) | __PPC_EH(eh))
-#define PPC_LOGMPP(b)		stringify_in_c(.long PPC_INST_LOGMPP | \
-					__PPC_RB(b))
+#define PPC_LOGMPP(a)		stringify_in_c(.long PPC_INST_LOGMPP | \
+					___PPC_RA(a))
 #define PPC_LWARX(t, a, b, eh)	stringify_in_c(.long PPC_INST_LWARX | \
 					___PPC_RT(t) | ___PPC_RA(a) | \
 					___PPC_RB(b) | __PPC_EH(eh))
-- 
2.1.4

             reply	other threads:[~2015-10-16  1:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16  1:20 Stewart Smith [this message]
2015-10-16  2:10 ` [PATCH] PPC: fix LOGMPP instruction opcode and inline asm Michael Ellerman
2015-10-16  3:53   ` Stewart Smith
2015-10-17 19:12 ` Jan Stancek

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=1444958435-18808-1-git-send-email-stewart@linux.vnet.ibm.com \
    --to=stewart@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=dgibson@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=stable@vger.kernel.org \
    --cc=thuth@redhat.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).