From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: "Aneesh Kumar K . V" <aneesh.kumar@linux.vnet.ibm.com>,
Nicholas Piggin <npiggin@gmail.com>
Subject: [PATCH 0/4] Fixes for SLB to C series
Date: Sat, 29 Sep 2018 02:00:54 +1000 [thread overview]
Message-ID: <20180928160058.18700-1-npiggin@gmail.com> (raw)
These are some fixes I've got so far to sovle hangs and multi hits
particularly on P8 with 256MB segments (but can also be reproduced
on P9).
I'm not yet sure these solve all the problems, and they need some
good review and testing. So far they have been solid for me.
Thanks,
Nick
Nicholas Piggin (4):
powerpc/64: add struct int_regs to save additional registers on stack
powerpc/64: interrupts save PPR on stack rather than thread_struct
powerpc/64s/hash: Fix preloading of SLB entries
powerpc/64s/hash: add more barriers for slb preloading
arch/powerpc/include/asm/exception-64s.h | 9 ++--
arch/powerpc/include/asm/processor.h | 12 +++---
arch/powerpc/include/asm/ptrace.h | 18 +++++---
arch/powerpc/kernel/asm-offsets.c | 23 ++++++----
arch/powerpc/kernel/entry_64.S | 15 +++----
arch/powerpc/kernel/process.c | 54 ++++++++++++------------
arch/powerpc/kernel/ptrace.c | 4 +-
arch/powerpc/kernel/stacktrace.c | 2 +-
arch/powerpc/mm/slb.c | 48 ++++++++++++++++++---
9 files changed, 116 insertions(+), 69 deletions(-)
--
2.18.0
next reply other threads:[~2018-09-28 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 16:00 Nicholas Piggin [this message]
2018-09-28 16:00 ` [PATCH 1/4] powerpc/64: add struct int_regs to save additional registers on stack Nicholas Piggin
2018-09-28 16:00 ` [PATCH 2/4] powerpc/64: interrupts save PPR on stack rather than thread_struct Nicholas Piggin
2018-09-28 16:00 ` [PATCH 3/4] powerpc/64s/hash: Fix preloading of SLB entries Nicholas Piggin
2018-09-28 16:00 ` [PATCH 4/4] powerpc/64s/hash: add more barriers for slb preloading Nicholas Piggin
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=20180928160058.18700-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.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).