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>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-mm@kvack.org
Subject: [PATCH v4 12/16] powerpc/8xx: split breakpoint exception
Date: Tue, 26 Nov 2019 12:36:16 +0000 (UTC) [thread overview]
Message-ID: <f9f926326ed150b2ab24ce362b14d97b76db7176.1574771541.git.christophe.leroy@c-s.fr> (raw)
In-Reply-To: <cover.1574771539.git.christophe.leroy@c-s.fr>
Breakpoint exception is big.
Split it to support future growth on exception prolog.
Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
---
arch/powerpc/kernel/head_8xx.S | 19 ++++++++++---------
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/arch/powerpc/kernel/head_8xx.S b/arch/powerpc/kernel/head_8xx.S
index 1e718e47fe3c..225e242ce1c5 100644
--- a/arch/powerpc/kernel/head_8xx.S
+++ b/arch/powerpc/kernel/head_8xx.S
@@ -490,14 +490,7 @@ DARFixed:/* Return from dcbx instruction bug workaround */
* support of breakpoints and such. Someday I will get around to
* using them.
*/
- . = 0x1c00
-DataBreakpoint:
- EXCEPTION_PROLOG_0
- mfspr r11, SPRN_SRR0
- cmplwi cr1, r11, (.Ldtlbie - PAGE_OFFSET)@l
- cmplwi cr7, r11, (.Litlbie - PAGE_OFFSET)@l
- beq- cr1, 11f
- beq- cr7, 11f
+do_databreakpoint:
EXCEPTION_PROLOG_1
EXCEPTION_PROLOG_2
addi r3,r1,STACK_FRAME_OVERHEAD
@@ -505,7 +498,15 @@ DataBreakpoint:
stw r4,_DAR(r11)
mfspr r5,SPRN_DSISR
EXC_XFER_STD(0x1c00, do_break)
-11:
+
+ . = 0x1c00
+DataBreakpoint:
+ EXCEPTION_PROLOG_0
+ mfspr r11, SPRN_SRR0
+ cmplwi cr1, r11, (.Ldtlbie - PAGE_OFFSET)@l
+ cmplwi cr7, r11, (.Litlbie - PAGE_OFFSET)@l
+ cror 4*cr1+eq, 4*cr1+eq, 4*cr7+eq
+ bne cr1, do_databreakpoint
mtcr r10
mfspr r10, SPRN_SPRG_SCRATCH0
mfspr r11, SPRN_SPRG_SCRATCH1
--
2.13.3
next prev parent reply other threads:[~2019-11-26 12:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 12:36 [PATCH v4 00/16] Enable CONFIG_VMAP_STACK on PPC32 Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 01/16] powerpc/32: replace MTMSRD() by mtmsr Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 02/16] powerpc/32: Add EXCEPTION_PROLOG_0 in head_32.h Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 03/16] powerpc/32: save DEAR/DAR before calling handle_page_fault Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 04/16] powerpc/32: move MSR_PR test into EXCEPTION_PROLOG_0 Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 05/16] powerpc/32: add a macro to get and/or save DAR and DSISR on stack Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 06/16] powerpc/32: prepare for CONFIG_VMAP_STACK Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 07/16] powerpc: align stack to 2 * THREAD_SIZE with VMAP_STACK Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 08/16] powerpc/32: Add early stack overflow detection with VMAP stack Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 09/16] powerpc/8xx: Use alternative scratch registers in DTLB miss handler Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 10/16] powerpc/8xx: drop exception entries for non-existing exceptions Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 11/16] powerpc/8xx: move DataStoreTLBMiss perf handler Christophe Leroy
2019-11-26 12:36 ` Christophe Leroy [this message]
2019-11-26 12:36 ` [PATCH v4 13/16] powerpc/8xx: Enable CONFIG_VMAP_STACK Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 14/16] powerpc/32s: reorganise DSI handler Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 15/16] powerpc/32s: avoid crossing page boundary while changing SRR0/1 Christophe Leroy
2019-11-26 12:36 ` [PATCH v4 16/16] powerpc/32s: Activate CONFIG_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=f9f926326ed150b2ab24ce362b14d97b76db7176.1574771541.git.christophe.leroy@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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;
as well as URLs for NNTP newsgroup(s).