From: David Daney <ddaney.cavm@gmail.com>
To: Alan Cooper <alcooperx@gmail.com>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org,
linux-kernel@vger.kernel.org
Subject: Re: MIPS Function Tracer question
Date: Thu, 29 Nov 2012 15:00:44 -0800 [thread overview]
Message-ID: <50B7E91C.6070403@gmail.com> (raw)
In-Reply-To: <CAOGqxeUOrVFoqsmUV19h5tXsD6pw5creXP9aN1C-V7K3WL2EXA@mail.gmail.com>
On 11/29/2012 01:04 PM, Alan Cooper wrote:
> I've been doing some testing of the MIPS Function Tracer functionality
> on the 3.3 kernel. I was surprised to find that the option to generate
> frame pointers was required for tracing.
It is not really required for MIPS function tracing, but the Kconfigs
for some reason set it.
> When I don't enable
> FRAME_POINTER along with FUNCTION_TRACER, the kernel hangs on boot. I
> also noticed that a checkin to the 3.4 kernel
> (b732d439cb43336cd6d7e804ecb2c81193ef63b0) no longer forces on
> FRAME_POINTER when FUNCTION_TRACER is selected. I was wondering how it
> works in 3.4 and beyond, so I built a Malta kernel from the latest
> MIPS tree with FUNCTION_TRACING enabled and tested it with QEMU. The
> kernel hung the same way. I can think of 2 reasons for this:
> 1. Function tracing is broken for MIPS in 3.4 and beyond.
> 2. The 4.5.3 GNU C compiler I'm using is generating different code for
> function tracing.
Function tracing works best with recent versions of GCC (those that
support -mmcount-ra-address).
> I was wondering if anyone has MIPS function tracing working in 3.4 or later?
Yes. Using GCC 4.7.0 on an octeon kernel (based on 3.4.14):
# tracer: function_graph
#
# CPU DURATION FUNCTION CALLS
# | | | | | | |
1) | __fsnotify_parent() {
1) 7.154 us | } /* __fsnotify_parent */
1) | fsnotify() {
1) | __srcu_read_lock() {
1) | add_preempt_count() {
1) 1.356 us | } /* add_preempt_count */
1) | sub_preempt_count() {
1) 1.385 us | } /* sub_preempt_count */
1) 6.747 us | } /* __srcu_read_lock */
1) | __srcu_read_unlock() {
1) | add_preempt_count() {
1) 1.383 us | } /* add_preempt_count */
1) | sub_preempt_count() {
1) 1.358 us | } /* sub_preempt_count */
1) 6.642 us | } /* __srcu_read_unlock */
1) + 17.861 us | } /* fsnotify */
.
.
.
>
> I did figure out why it's hanging and I have some changes that will
> allow the function tracer to run without frame pointers, but before I
> proceed I want to rule out compiler differences.
>
> Thanks
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2012-11-29 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 21:04 MIPS Function Tracer question Alan Cooper
2012-11-29 23:00 ` David Daney [this message]
[not found] ` <CAOGqxeU=BumDt6jnVc=sKk=q_v1eywGu=_Eo9xo3r9av3Ky6kw@mail.gmail.com>
2012-11-30 16:25 ` David Daney
2012-12-03 14:40 ` Steven Rostedt
2012-12-03 16:13 ` Ralf Baechle
2012-12-03 17:50 ` 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=50B7E91C.6070403@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=alcooperx@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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