From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
npiggin@gmail.com, dja@axtens.net
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: [RFC PATCH v2 00/10] Enable CONFIG_VMAP_STACK on PPC32
Date: Sat, 31 Aug 2019 10:18:23 +0000 (UTC) [thread overview]
Message-ID: <cover.1567245404.git.christophe.leroy@c-s.fr> (raw)
The purpose of this serie is to enable CONFIG_VMAP_STACK on PPC32.
For the time being we have something working on 8xx.
Further work I'm working on:
- Fix stack overflow detection (doesn't work all the time yet, with the LKDTM STACK_EXHAUST test it hang).
- Add support to powerpc 603
- Add support to all book3s32
v2: added stack overflow detection.
Christophe Leroy (10):
powerpc/32: replace MTMSRD() by mtmsr
powerpc/32: Add EXCEPTION_PROLOG_0 in head_32.h
powerpc/32: prepare for CONFIG_VMAP_STACK
powerpc/8xx: Use alternative scratch registers in DTLB miss handler
powerpc/8xx: drop exception entries for non-existing exceptions
powerpc/8xx: move DataStoreTLBMiss perf handler
powerpc/8xx: split breakpoint exception
powerpc/8xx: Enable CONFIG_VMAP_STACK
powerpc: align stack to 2 * THREAD_SIZE with VMAP_STACK
powerpc/32: Add stack overflow detection with VMAP stack.
arch/powerpc/Kconfig | 1 +
arch/powerpc/include/asm/processor.h | 5 ++
arch/powerpc/include/asm/thread_info.h | 18 ++++
arch/powerpc/kernel/asm-offsets.c | 5 ++
arch/powerpc/kernel/entry_32.S | 37 +++++++--
arch/powerpc/kernel/head_32.S | 4 +-
arch/powerpc/kernel/head_32.h | 98 ++++++++++++++++++++--
arch/powerpc/kernel/head_8xx.S | 145 ++++++++++++++++++---------------
arch/powerpc/kernel/setup_32.c | 2 +-
arch/powerpc/kernel/setup_64.c | 2 +-
arch/powerpc/kernel/vmlinux.lds.S | 2 +-
arch/powerpc/perf/8xx-pmu.c | 12 ++-
12 files changed, 240 insertions(+), 91 deletions(-)
--
2.13.3
next reply other threads:[~2019-08-31 10:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 10:18 Christophe Leroy [this message]
2019-08-31 10:18 ` [RFC PATCH v2 01/10] powerpc/32: replace MTMSRD() by mtmsr Christophe Leroy
2019-08-31 10:18 ` [RFC PATCH v2 02/10] powerpc/32: Add EXCEPTION_PROLOG_0 in head_32.h Christophe Leroy
2019-08-31 10:18 ` [RFC PATCH v2 03/10] powerpc/32: prepare for CONFIG_VMAP_STACK Christophe Leroy
2019-08-31 10:18 ` [RFC PATCH v2 04/10] powerpc/8xx: Use alternative scratch registers in DTLB miss handler Christophe Leroy
2019-08-31 10:18 ` [RFC PATCH v2 05/10] powerpc/8xx: drop exception entries for non-existing exceptions Christophe Leroy
2019-08-31 10:18 ` [RFC PATCH v2 06/10] powerpc/8xx: move DataStoreTLBMiss perf handler Christophe Leroy
2019-08-31 10:18 ` [RFC PATCH v2 07/10] powerpc/8xx: split breakpoint exception Christophe Leroy
2019-08-31 10:18 ` [RFC PATCH v2 08/10] powerpc/8xx: Enable CONFIG_VMAP_STACK Christophe Leroy
2019-08-31 10:18 ` [RFC PATCH v2 09/10] powerpc: align stack to 2 * THREAD_SIZE with VMAP_STACK Christophe Leroy
2019-08-31 10:18 ` [RFC PATCH v2 10/10] powerpc/32: Add stack overflow detection with VMAP stack Christophe Leroy
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=cover.1567245404.git.christophe.leroy@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=benh@kernel.crashing.org \
--cc=dja@axtens.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®