diff options
author | Nikolay Borisov <Nikolay.Borisov@arm.com> | 2014-06-03 19:48:10 +0100 |
---|---|---|
committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2014-07-18 12:29:11 +0100 |
commit | 9865f1d46a68a5f58cb623054c8308484007d8a4 (patch) | |
tree | f20a30ff2e839e9dab1a04204cc44904c22a821d /arch/arm/kernel/perf_event.c | |
parent | 9696fcae9251610f5935a3823be40d1365649720 (diff) | |
download | linux-stable-9865f1d46a68a5f58cb623054c8308484007d8a4.tar.gz linux-stable-9865f1d46a68a5f58cb623054c8308484007d8a4.tar.bz2 linux-stable-9865f1d46a68a5f58cb623054c8308484007d8a4.zip |
ARM: 8070/1: Introduce arm_get_current_stack_frame()
Currently there are numerous places where "struct pt_regs" are used to
populate "struct stackframe", however all of those location do not
consider the situation where the kernel might be compiled in THUMB2
mode, in which case the framepointer member of pt_regs become ARM_r7
instead of ARM_fp (r11). Document this idiosyncracy in the
definition of "struct stackframe"
The easiest solution is to introduce a new function (in the spirit of
https://groups.google.com/forum/#!topic/linux.kernel/dA2YuUcSpZ4)
which would hide the complexity of initializing the stackframe struct
from pt_regs.
Also implement a macro frame_pointer(regs) that would return the correct
register so that we can use it in cases where we just require the frame
pointer and not a whole struct stackframe
Signed-off-by: Nikolay Borisov <Nikolay.Borisov@arm.com>
Acked-by: Will Deacon <will.deacon@arm.com>
Acked-by: Robert Richter <rric@kernel.org>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'arch/arm/kernel/perf_event.c')
0 files changed, 0 insertions, 0 deletions