From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joel@joelfernandes.org>,
Jiping Ma <jiping.ma2@windriver.com>,
mingo@redhat.com, catalin.marinas@arm.com, will.deacon@arm.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] tracing: Document the stack trace algorithm in the comments
Date: Wed, 7 Aug 2019 12:40:13 -0400 [thread overview]
Message-ID: <20190807124013.4ced2f81@gandalf.local.home> (raw)
In-Reply-To: <20190807163454.392141426@goodmis.org>
On Wed, 07 Aug 2019 12:34:03 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
> + * To fix this, if the architecture sets ARCH_RET_ADDR_AFTER_LOCAL_VARS the
> + * values in stack_trace_index[] are shifted by one to and the number of
> + * stack trace entries is decremented by one.
> + *
> + * stack_dump_trace[] | stack_trace_index[]
> + * ------------------ + -------------------
> + * return addr to kernel_func_bar | 20
That should have been 29, not 20. I'll update it.
-- Steve
> + * return addr to sys_foo | 19
> + *
> + * Although the entry function is not displayed, the first function (sys_foo)
> + * will still include the stack size of it.
> + */
> static void check_stack(unsigned long ip, unsigned long *stack)
> {
> unsigned long this_size, flags; unsigned long *p, *top, *start;
next prev parent reply other threads:[~2019-08-07 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 16:34 [PATCH 0/2] tracing/arm: Fix the stack tracer when LR is saved after local storage Steven Rostedt
2019-08-07 16:34 ` [PATCH 1/2] tracing/arm64: Have max stack tracer handle the case of return address after data Steven Rostedt
2019-08-07 16:34 ` [PATCH 2/2] tracing: Document the stack trace algorithm in the comments Steven Rostedt
2019-08-07 16:40 ` Steven Rostedt [this message]
2019-08-07 17:08 ` [PATCH 0/2] tracing/arm: Fix the stack tracer when LR is saved after local storage Mark Rutland
2019-08-07 17:20 ` Steven Rostedt
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=20190807124013.4ced2f81@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=catalin.marinas@arm.com \
--cc=jiping.ma2@windriver.com \
--cc=joel@joelfernandes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®