From: Michael Ellerman <michael@ellerman.id.au>
To: <linuxppc-dev@ozlabs.org>
Subject: [PATCH 2/6] powerpc/pseries: Add a warning in the case of cross-cpu VPA registration
Date: Thu, 15 Aug 2013 15:22:15 +1000 [thread overview]
Message-ID: <1376544139-26783-2-git-send-email-michael@ellerman.id.au> (raw)
In-Reply-To: <1376544139-26783-1-git-send-email-michael@ellerman.id.au>
The spec says it "may be problematic" if CPU x registers the VPA of
CPU y. Add a warning in case we ever do that.
Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
---
arch/powerpc/platforms/pseries/lpar.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/powerpc/platforms/pseries/lpar.c b/arch/powerpc/platforms/pseries/lpar.c
index 8bad880..73d6c1b 100644
--- a/arch/powerpc/platforms/pseries/lpar.c
+++ b/arch/powerpc/platforms/pseries/lpar.c
@@ -68,6 +68,12 @@ void vpa_init(int cpu)
struct paca_struct *pp;
struct dtl_entry *dtl;
+ /*
+ * The spec says it "may be problematic" if CPU x registers the VPA of
+ * CPU y. We should never do that, but wail if we ever do.
+ */
+ WARN_ON(cpu != smp_processor_id());
+
if (cpu_has_feature(CPU_FTR_ALTIVEC))
lppaca_of(cpu).vmxregs_in_use = 1;
--
1.8.1.2
next prev parent reply other threads:[~2013-08-15 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 5:22 [PATCH 1/6] powerpc: Update the 00-Index in Documentation/powerpc Michael Ellerman
2013-08-15 5:22 ` Michael Ellerman [this message]
2013-08-15 5:22 ` [PATCH 3/6] powerpc: Add more trap names to xmon Michael Ellerman
2013-08-20 10:52 ` Paul Mackerras
2013-08-15 5:22 ` [PATCH 4/6] powerpc: Fix location and rename exception trampolines Michael Ellerman
2013-08-15 5:22 ` [PATCH 5/6] powerpc: Add more exception trampolines for hypervisor exceptions Michael Ellerman
2013-08-15 5:22 ` [PATCH 6/6] powerpc: Skip emulating & leave interrupts off for kernel program checks Michael Ellerman
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=1376544139-26783-2-git-send-email-michael@ellerman.id.au \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
/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).