From: Wu Zhangjin <wuzhangjin@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Nicholas Mc Guire <hofrat@hofr.at>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
zhangfx@lemote.com, loongson-dev@googlegroups.com,
yanh@lemote.com, Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, Zhang Le <r0bertz@gentoo.org>,
linux-rt-users@vger.kernel.org
Subject: "RT_PREEMPT for loongson" is updated to patch-2.6.29.1-rt8
Date: Mon, 20 Apr 2009 10:12:27 +0800 [thread overview]
Message-ID: <1240193547.25532.52.camel@falcon> (raw)
hi, all
I just update "RT_PREEMPT for loongson" to the latest RT_PREEMPT
(patch-2.6.29.1-rt8), welcome to pull & test it.
$ git clone git://dev.lemote.com/rt4ls.git
or
http://dev.lemote.com/http_git/rt4ls.git
this version include basic-RT support for mips, ftrace support for mips
(static function tracer/dynamic function tracer/function graph
tracer/system call tracer).
* current status
the "system call tracer" need to fix when compiled in 64bit, because
there are several sys_call_table entries for different mips64
standards(o32, n32), currently, i only use the one in
arch/mips/kernel/scall64-o32.S via EXPORT(sys_call_table).
the "function graph tracer" is not stable under 100% load(lots of
"find /" background).
best regards,
Wu Zhangjin
--
Wu Zhangjin
DSLab, Lanzhou University, China
www.lemote.com, Jiangsu Province, China
next reply other threads:[~2009-04-20 2:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 2:12 Wu Zhangjin [this message]
2009-04-20 5:04 ` "RT_PREEMPT for loongson" is updated to patch-2.6.29.1-rt8 Zhang Le
2009-04-20 7:18 ` Wu Zhangjin
2009-04-20 8:01 ` Ralf Baechle
2009-04-20 13:10 ` Ralf Baechle
2009-04-20 14:22 ` Wu Zhangjin
2009-04-28 12:29 ` Ralf Baechle
2009-04-28 15:57 ` Wu Zhangjin
2009-04-28 17:21 ` Wu Zhangjin
2009-04-29 19:38 ` Wu Zhangjin
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=1240193547.25532.52.camel@falcon \
--to=wuzhangjin@gmail.com \
--cc=hofrat@hofr.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=loongson-dev@googlegroups.com \
--cc=mingo@elte.hu \
--cc=r0bertz@gentoo.org \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=yanh@lemote.com \
--cc=zhangfx@lemote.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;
as well as URLs for NNTP newsgroup(s).