Commit 1db550f4 authored by Andrew Donnellan's avatar Andrew Donnellan Committed by Michael Ellerman

powerpc/64s/exception: Fix kaup -> kuap typo

It's KUAP, not KAUP. Fix typo in INT_COMMON macro.
Signed-off-by: default avatarAndrew Donnellan <ajd@linux.ibm.com>
Signed-off-by: default avatarMichael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20191022060603.24101-1-ajd@linux.ibm.com
parent bbbd7f11
...@@ -514,7 +514,7 @@ END_FTR_SECTION_NESTED(CPU_FTR_HAS_PPR,CPU_FTR_HAS_PPR,948) ...@@ -514,7 +514,7 @@ END_FTR_SECTION_NESTED(CPU_FTR_HAS_PPR,CPU_FTR_HAS_PPR,948)
* If stack=0, then the stack is already set in r1, and r1 is saved in r10. * If stack=0, then the stack is already set in r1, and r1 is saved in r10.
* PPR save and CPU accounting is not done for the !stack case (XXX why not?) * PPR save and CPU accounting is not done for the !stack case (XXX why not?)
*/ */
.macro INT_COMMON vec, area, stack, kaup, reconcile, dar, dsisr .macro INT_COMMON vec, area, stack, kuap, reconcile, dar, dsisr
.if \stack .if \stack
andi. r10,r12,MSR_PR /* See if coming from user */ andi. r10,r12,MSR_PR /* See if coming from user */
mr r10,r1 /* Save r1 */ mr r10,r1 /* Save r1 */
...@@ -533,7 +533,7 @@ END_FTR_SECTION_NESTED(CPU_FTR_HAS_PPR,CPU_FTR_HAS_PPR,948) ...@@ -533,7 +533,7 @@ END_FTR_SECTION_NESTED(CPU_FTR_HAS_PPR,CPU_FTR_HAS_PPR,948)
std r10,GPR1(r1) /* save r1 in stackframe */ std r10,GPR1(r1) /* save r1 in stackframe */
.if \stack .if \stack
.if \kaup .if \kuap
kuap_save_amr_and_lock r9, r10, cr1, cr0 kuap_save_amr_and_lock r9, r10, cr1, cr0
.endif .endif
beq 101f /* if from kernel mode */ beq 101f /* if from kernel mode */
...@@ -541,7 +541,7 @@ END_FTR_SECTION_NESTED(CPU_FTR_HAS_PPR,CPU_FTR_HAS_PPR,948) ...@@ -541,7 +541,7 @@ END_FTR_SECTION_NESTED(CPU_FTR_HAS_PPR,CPU_FTR_HAS_PPR,948)
SAVE_PPR(\area, r9) SAVE_PPR(\area, r9)
101: 101:
.else .else
.if \kaup .if \kuap
kuap_save_amr_and_lock r9, r10, cr1 kuap_save_amr_and_lock r9, r10, cr1
.endif .endif
.endif .endif
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment