public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: john cooper <john.cooper@third-harmonic.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: MIPS RT debug support
Date: Thu, 15 Nov 2007 15:31:45 -0800	[thread overview]
Message-ID: <473CD6E1.1060607@am.sony.com> (raw)
In-Reply-To: <473BADD4.5030400@third-harmonic.com>

john cooper wrote:
> The more daunting problem stems from limitations in the MIPS
> ABI which makes the latency trace support problematic.
> Rather than rehash the issue:
> 
>     http://lists.linuxcoding.com/kernel/2005-q4/msg10163.html
> 
> Until we have a usable instrumentation solution in place,
> characterization, debug, and support of PREEMPT_RT for MIPS
> is going to be a challenge.

Agreed.  I have been using KFT (Kernel Function Trace)
on MIPS, and it has decent support for function traceback
reporting, but it's not currently integrated with latency-trace
at all.   We should discuss if this could possibly be
used to debug RT-preempt.  It is much heavier weight than
the mcount stuff, but uses similar (but not identical)
gcc profiling instrumentation.  I'm not sure if the
two can be turned on together, or how hard it would
be to move latency-trace onto -finstrument_functions.

But it's probably worth researching a little.  We'll
need something to give insight into the problem paths.
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================


  reply	other threads:[~2007-11-15 23:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15  0:15 rt-preempt: problem compiling rt-preempt 2.6.23.1-rt11 on MIPS Tim Bird
2007-11-15  0:56 ` Thomas Gleixner
2007-11-15  1:06   ` Steven Rostedt
2007-11-15  1:20     ` Tim Bird
2007-11-15  1:27       ` Steven Rostedt
2007-11-15  2:24   ` john cooper
2007-11-15 23:31     ` Tim Bird [this message]
2007-11-16  1:00       ` MIPS RT debug support Steven Rostedt
2007-11-16  1:55         ` john cooper
2007-11-16  2:25           ` Steven Rostedt
2007-11-16 11:56             ` john cooper

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=473CD6E1.1060607@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=john.cooper@third-harmonic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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