public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: mingo@elte.hu, srostedt@redhat.com
Cc: linux-kernel@vger.kernel.org,
	John Williams <john.williams@petalogix.com>,
	linux-kernel@vger.kernel.org
Subject: Ftrace for Microblaze - notrace
Date: Tue, 03 Nov 2009 14:32:30 +0100	[thread overview]
Message-ID: <4AF030EE.7050609@monstr.eu> (raw)

Hi Thomas, Ingo, Steven and others

I am working on ftrace support for Microblaze. I have done basic ftrace
support - initcall, kmemtrace and other.
Currently I am working on function trace support.  I did asm code as is
written in Documentation/trace/ftrace-design.txt.

I have two poins/questions.

I desided to use HAVE_FUNCTION_TRACE_MCOUNT_TEST - just test 
function_trace_stop in asm code - that shouldn't be a problem.

I disable -pg in main Makefile because not work for me (more info below) 
and I enable it just for two file in arch/microblaze (irq.c and intc.c) 
- recompile kernel and test. Log is below and you can see that I am able 
to see output for function. That's why I think that my mcount function 
should be correct. Am I right?

uclinux login: root
Password:
# cd ; mkdir /debug; mount -t debugfs none /debug; cat 
/debug/tracing/available_
tracers; echo function > /debug/tracing/current_tracer;echo 1 > 
/debug/tracing/t
racing_enabled;cat /debug/tracing/trace | head -n 10
wakeup_rt wakeup function sched_switch nop
# tracer: function
#
#           TASK-PID    CPU#    TIMESTAMP  FUNCTION
#              | |       |          |         |
               sh-52    [000]   184.940000: irq_call <-do_IRQ
               sh-52    [000]   184.940000: do_IRQ <-get_irq
               sh-52    [000]   184.940000: handle_level_irq <-intc_mask_ack
               sh-52    [000]   184.950000: handle_level_irq 
<-intc_enable_or_unmask
               sh-52    [000]   184.950000: do_IRQ <-get_irq
               sh-52    [000]   184.950000: handle_level_irq <-intc_mask_ack
#


When is used -pg flag kernel stops when I enable function tracer.
Interesting is that freeze than I setup function tracing (echo function 
 > .../current/tracer). Is it correct behavior? I think that trace 
should start after (echo 1>  .../tracing_enabled).


The next thing is about annotation notrace. I look at all arch. Is there 
any algorithm which function should use it? I think that this could be a 
  reason why I my kernel freeze when enable function tracer.

I tested to add -pg flag for process.c file and after it kernel freeze 
too. Is it mean that problem could be there?

Any other suggestion?


Thanks for your help,
Michal



             reply	other threads:[~2009-11-03 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 13:32 Michal Simek [this message]
2009-11-03 16:35 ` Ftrace for Microblaze - notrace Steven Rostedt
2009-11-03 16:45   ` Michal Simek
2009-11-03 17:32     ` Steven Rostedt
2009-11-03 18:11       ` Michal Simek
2009-11-04  2:03         ` Steven Rostedt
2009-11-04  2:26           ` John Williams
2009-11-04  2:42             ` 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=4AF030EE.7050609@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=john.williams@petalogix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=srostedt@redhat.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