summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorArun Sharma <asharma@fb.com>2012-04-20 15:41:33 -0700
committerIngo Molnar <mingo@kernel.org>2012-06-06 17:07:58 +0200
commit302fa4b58ac754a6da13f4f5546f710fecc3b945 (patch)
tree6df70de7ed659a0c5b670c781a2022386aaa0732 /include
parent8440ccb43fc0ecffcf1acee0273d766e6a8cd51d (diff)
downloadlinux-stable-302fa4b58ac754a6da13f4f5546f710fecc3b945.tar.gz
linux-stable-302fa4b58ac754a6da13f4f5546f710fecc3b945.tar.bz2
linux-stable-302fa4b58ac754a6da13f4f5546f710fecc3b945.zip
perf/x86: Allow multiple stacks
Without this patch, applications with two different stack regions (eg: native stack vs JIT stack) get truncated callchains even when RBP chaining is present. GDB shows proper stack traces and the frame pointer chaining is intact. This patch disables the (fp < RSP) check, hoping that other checks in the code save the day for us. In our limited testing, this didn't seem to break anything. In the long term, we could potentially have userspace advise the kernel on the range of valid stack addresses, so we don't spend a lot of time unwinding from bogus addresses. Signed-off-by: Arun Sharma <asharma@fb.com> CC: Arnaldo Carvalho de Melo <acme@redhat.com> Cc: Frederic Weisbecker <fweisbec@gmail.com> Cc: Mike Galbraith <efault@gmx.de> Cc: Paul Mackerras <paulus@samba.org> Cc: Stephane Eranian <eranian@google.com> Cc: Namhyung Kim <namhyung.kim@lge.com> Cc: Tom Zanussi <tzanussi@gmail.com> Cc: linux-kernel@vger.kernel.org Cc: linux-perf-users@vger.kernel.org Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Link: http://lkml.kernel.org/r/1334961696-19580-2-git-send-email-asharma@fb.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions