From: Steven Rostedt <rostedt@goodmis.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: Jiping Ma <jiping.ma2@windriver.com>,
mingo@redhat.com, catalin.marinas@arm.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] tracing: Function stack size and its name mismatch in arm64
Date: Tue, 6 Aug 2019 13:03:23 -0400 [thread overview]
Message-ID: <20190806130323.7075c3da@gandalf.local.home> (raw)
In-Reply-To: <20190806123455.487ac02b@gandalf.local.home>
On Tue, 6 Aug 2019 12:34:55 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> Here's the best way to explain this. The code is using the stack trace
> to figure out which function is the stack hog. Or perhaps a serious of
Why so serious? .... s/serious/series/
-- Steve
> stack hogs. On x86, a call stores the return address as it calls the
> next function. Then that function allocates its stack frame for its
> local variables and saving of registers.
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: Jiping Ma <jiping.ma2@windriver.com>,
catalin.marinas@arm.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] tracing: Function stack size and its name mismatch in arm64
Date: Tue, 6 Aug 2019 13:03:23 -0400 [thread overview]
Message-ID: <20190806130323.7075c3da@gandalf.local.home> (raw)
In-Reply-To: <20190806123455.487ac02b@gandalf.local.home>
On Tue, 6 Aug 2019 12:34:55 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> Here's the best way to explain this. The code is using the stack trace
> to figure out which function is the stack hog. Or perhaps a serious of
Why so serious? .... s/serious/series/
-- Steve
> stack hogs. On x86, a call stores the return address as it calls the
> next function. Then that function allocates its stack frame for its
> local variables and saving of registers.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-06 17:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 9:41 [PATCH v3] tracing: Function stack size and its name mismatch in arm64 Jiping Ma
2019-08-02 15:22 ` Steven Rostedt
2019-08-02 15:22 ` Steven Rostedt
2019-08-02 16:09 ` Steven Rostedt
2019-08-02 16:09 ` Steven Rostedt
2019-08-02 16:11 ` Steven Rostedt
2019-08-02 16:11 ` Steven Rostedt
2019-08-06 15:48 ` Joel Fernandes
2019-08-06 15:48 ` Joel Fernandes
2019-08-06 16:34 ` Steven Rostedt
2019-08-06 16:34 ` Steven Rostedt
2019-08-06 17:03 ` Steven Rostedt [this message]
2019-08-06 17:03 ` Steven Rostedt
2019-08-06 17:25 ` Joel Fernandes
2019-08-06 17:25 ` Joel Fernandes
2019-08-06 6:01 ` Jiping Ma
2019-08-03 8:26 ` Joel Fernandes
2019-08-03 8:26 ` Joel Fernandes
2019-08-03 8:32 ` Joel Fernandes
2019-08-03 8:32 ` Joel Fernandes
2019-08-05 11:25 ` Will Deacon
2019-08-05 11:25 ` Will Deacon
2019-08-05 13:59 ` Steven Rostedt
2019-08-05 13:59 ` Steven Rostedt
2019-08-06 13:00 ` Steven Rostedt
2019-08-06 13:00 ` Steven Rostedt
2019-08-06 14:47 ` Joel Fernandes
2019-08-06 14:47 ` Joel Fernandes
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=20190806130323.7075c3da@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.