From: behanw@converseincode.com (behanw at converseincode.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 5/6] arm64: LLVMLinux: Use global stack register variable for aarch64
Date: Tue, 26 Aug 2014 21:29:33 -0700 [thread overview]
Message-ID: <1409113774-3172-6-git-send-email-behanw@converseincode.com> (raw)
In-Reply-To: <1409113774-3172-1-git-send-email-behanw@converseincode.com>
From: Mark Charlebois <charlebm@gmail.com>
To support both Clang and GCC, use the global stack register variable vs
a local register variable.
Author: Mark Charlebois <charlebm@gmail.com>
Signed-off-by: Mark Charlebois <charlebm@gmail.com>
Signed-off-by: Behan Webster <behanw@converseincode.com>
---
arch/arm64/include/asm/percpu.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/include/asm/percpu.h b/arch/arm64/include/asm/percpu.h
index 453a179..5279e57 100644
--- a/arch/arm64/include/asm/percpu.h
+++ b/arch/arm64/include/asm/percpu.h
@@ -26,13 +26,13 @@ static inline void set_my_cpu_offset(unsigned long off)
static inline unsigned long __my_cpu_offset(void)
{
unsigned long off;
- register unsigned long *sp asm ("sp");
/*
* We want to allow caching the value, so avoid using volatile and
* instead use a fake stack read to hazard against barrier().
*/
- asm("mrs %0, tpidr_el1" : "=r" (off) : "Q" (*sp));
+ asm("mrs %0, tpidr_el1" : "=r" (off) :
+ "Q" (*(const unsigned long *)current_stack_pointer));
return off;
}
--
1.9.1
next prev parent reply other threads:[~2014-08-27 4:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 23:57 [PATCH 0/4] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM behanw at converseincode.com
2014-07-30 23:57 ` [PATCH 1/4] arm64: LLVMLinux: Add current_stack_pointer() for arm64 behanw at converseincode.com
2014-07-30 23:57 ` [PATCH 2/4] arm64: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk behanw at converseincode.com
2014-07-30 23:57 ` [PATCH 3/4] arm64: LLVMLinux: Calculate current_thread_info from current_stack_pointer behanw at converseincode.com
2014-07-31 5:31 ` Andreas Färber
2014-07-31 16:04 ` Behan Webster
2014-07-30 23:57 ` [PATCH 4/4] arm64: LLVMLinux: Use current_stack_pointer in kernel/traps.c behanw at converseincode.com
2014-07-31 0:11 ` [PATCH 0/4] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM Olof Johansson
2014-07-31 10:33 ` Will Deacon
2014-07-31 15:39 ` Olof Johansson
2014-07-31 15:48 ` Will Deacon
2014-07-31 15:52 ` Olof Johansson
2014-08-01 4:11 ` Behan Webster
2014-08-26 14:16 ` Will Deacon
2014-08-27 4:26 ` Behan Webster
2014-08-27 4:29 ` [PATCH V2 0/6] " behanw at converseincode.com
2014-08-27 4:29 ` [PATCH V2 1/6] arm64: LLVMLinux: Add current_stack_pointer() for arm64 behanw at converseincode.com
2014-08-27 4:29 ` [PATCH V2 2/6] arm64: LLVMLinux: Use current_stack_pointer in save_stack_trace_tsk behanw at converseincode.com
2014-08-27 4:29 ` [PATCH V2 3/6] arm64: LLVMLinux: Calculate current_thread_info from current_stack_pointer behanw at converseincode.com
2014-08-27 4:29 ` [PATCH V2 4/6] arm64: LLVMLinux: Use current_stack_pointer in kernel/traps.c behanw at converseincode.com
2014-08-27 4:29 ` behanw at converseincode.com [this message]
2014-08-27 4:29 ` [PATCH V2 6/6] arm64: LLVMLinux: Use global stack pointer in return_address() behanw at converseincode.com
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=1409113774-3172-6-git-send-email-behanw@converseincode.com \
--to=behanw@converseincode.com \
--cc=linux-arm-kernel@lists.infradead.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).