[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1409113774-3172-3-git-send-email-behanw@converseincode.com>
Date: Tue, 26 Aug 2014 21:29:30 -0700
From: behanw@...verseincode.com
To: ard.biesheuvel@...aro.org, catalin.marinas@....com,
cl@...ux-foundation.org, jays.lee@...sung.com,
k.khlebnikov@...sung.com, larry.bassel@...aro.org, olof@...om.net,
peterz@...radead.org, takahiro.akashi@...aro.org,
tglx@...utronix.de, tj@...nel.org, will.deacon@....com
Cc: christoffer.dall@...aro.org, kgene.kim@...sung.com,
khilman@...aro.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, sungjinn.chung@...sung.com,
Behan Webster <behanw@...verseincode.com>,
Mark Charlebois <charlebm@...il.com>
Subject: [PATCH V2 2/6] arm64: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk
From: Behan Webster <behanw@...verseincode.com>
Use the global current_stack_pointer to get the value of the stack pointer.
This change supports being able to compile the kernel with both gcc and clang.
Signed-off-by: Behan Webster <behanw@...verseincode.com>
Signed-off-by: Mark Charlebois <charlebm@...il.com>
Reviewed-by: Jan-Simon Möller <dl9pf@....de>
Reviewed-by: Olof Johansson <olof@...om.net>
Acked-by: Will Deacon <will.deacon@....com>
---
arch/arm64/kernel/stacktrace.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/arm64/kernel/stacktrace.c b/arch/arm64/kernel/stacktrace.c
index 55437ba..407991b 100644
--- a/arch/arm64/kernel/stacktrace.c
+++ b/arch/arm64/kernel/stacktrace.c
@@ -111,10 +111,9 @@ void save_stack_trace_tsk(struct task_struct *tsk, struct stack_trace *trace)
frame.sp = thread_saved_sp(tsk);
frame.pc = thread_saved_pc(tsk);
} else {
- register unsigned long current_sp asm("sp");
data.no_sched_functions = 0;
frame.fp = (unsigned long)__builtin_frame_address(0);
- frame.sp = current_sp;
+ frame.sp = current_stack_pointer;
frame.pc = (unsigned long)save_stack_trace_tsk;
}
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists