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 v2 0/9] Fixes for SLB to C series
Date: Wed, 3 Oct 2018 00:27:50 +1000 [thread overview]
Message-ID: <20181002142759.6244-1-npiggin@gmail.com> (raw)
This is another spin of the fixes. Also painfully re-discovered
that we need https://patchwork.ozlabs.org/patch/962327/, as it
prevents POWER8 NUMA from booting (initial stack SLB for the
!0 node CPUs gets cleared by the initial TLB flush without it,
and the SLB handler now uses the stack...)
Question is whether to revert the series and try again next time.
I'm inclined to maybe say revert because it's been holdig up the
tree a bit and also some of these patches like the PPR fixes are
pretty complicated and should really be done as pre-requisites rather
than fixes.
Thanks,
Nick
Nicholas Piggin (9):
Revert "powerpc/64s/hash: remove user SLB data from the paca"
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
powerpc/64s/hash: SLB fix preemption issues
powerpc/64s/hash: Fix false positive preempt warnings
powerpc/64s/hash: slb_flush_and_rebolt simplify
powerpc/64s/hash: add some slb debugging tests
arch/powerpc/include/asm/book3s/64/mmu-hash.h | 3 +-
arch/powerpc/include/asm/exception-64s.h | 9 +-
arch/powerpc/include/asm/paca.h | 16 ++
arch/powerpc/include/asm/processor.h | 12 +-
arch/powerpc/include/asm/ptrace.h | 18 +-
arch/powerpc/kernel/asm-offsets.c | 32 ++-
arch/powerpc/kernel/entry_64.S | 15 +-
arch/powerpc/kernel/paca.c | 22 ++
arch/powerpc/kernel/process.c | 54 ++---
arch/powerpc/kernel/ptrace.c | 4 +-
arch/powerpc/kernel/stacktrace.c | 2 +-
arch/powerpc/kernel/swsusp_asm64.S | 2 +-
arch/powerpc/mm/hash_utils_64.c | 46 +++-
arch/powerpc/mm/mmu_context.c | 3 +-
arch/powerpc/mm/slb.c | 203 ++++++++++++------
arch/powerpc/mm/slice.c | 29 ++-
16 files changed, 314 insertions(+), 156 deletions(-)
--
2.18.0
next reply other threads:[~2018-10-02 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 14:27 Nicholas Piggin [this message]
2018-10-02 14:27 ` [PATCH v2 1/9] Revert "powerpc/64s/hash: remove user SLB data from the paca" Nicholas Piggin
2018-10-02 14:27 ` [PATCH v2 2/9] powerpc/64: add struct int_regs to save additional registers on stack Nicholas Piggin
2018-10-02 14:27 ` [PATCH v2 3/9] powerpc/64: interrupts save PPR on stack rather than thread_struct Nicholas Piggin
2018-10-02 14:27 ` [PATCH v2 4/9] powerpc/64s/hash: Fix preloading of SLB entries Nicholas Piggin
2018-10-02 14:27 ` [PATCH v2 5/9] powerpc/64s/hash: add more barriers for slb preloading Nicholas Piggin
2018-10-02 14:27 ` [PATCH v2 6/9] powerpc/64s/hash: SLB fix preemption issues Nicholas Piggin
2018-10-02 14:27 ` [PATCH v2 7/9] powerpc/64s/hash: Fix false positive preempt warnings Nicholas Piggin
2018-10-02 14:27 ` [PATCH v2 8/9] powerpc/64s/hash: slb_flush_and_rebolt simplify Nicholas Piggin
2018-10-02 14:27 ` [PATCH v2 9/9] powerpc/64s/hash: add some slb debugging tests 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=20181002142759.6244-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).