From: john cooper <john.cooper@third-harmonic.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Tim Bird <tim.bird@am.sony.com>,
linux kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
john cooper <john.cooper@third-harmonic.com>
Subject: Re: rt-preempt: problem compiling rt-preempt 2.6.23.1-rt11 on MIPS
Date: Wed, 14 Nov 2007 21:24:20 -0500 [thread overview]
Message-ID: <473BADD4.5030400@third-harmonic.com> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711150143220.3265@localhost.localdomain>
Thomas Gleixner wrote:
> I fear you are the one who is in charge to get mips working again :)
> But as always, there are bad news and good news: As far as I heard
> last week John Cooper is looking into this as well.
I'm not actively working on it but AFAIK I may have been
the last one to touch it when I did the mips version back
at Timesys. Although I was able to get a functional port
of the work there were gremlins I never had sufficient
time to address. That is a relatively minor issue.
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.
-john
--
john.cooper@third-harmonic.com
next prev parent reply other threads:[~2007-11-15 2:33 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 [this message]
2007-11-15 23:31 ` MIPS RT debug support Tim Bird
2007-11-16 1:00 ` 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=473BADD4.5030400@third-harmonic.com \
--to=john.cooper@third-harmonic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.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.