From: Ralf Baechle <ralf@linux-mips.org>
To: Wu Zhangjin <wuzhangjin@gmail.com>
Cc: Zhang Le <r0bertz@gentoo.org>,
linux-kernel@vger.kernel.org, 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, linux-mips@linux-mips.org,
linux-rt-users@vger.kernel.org
Subject: Re: "RT_PREEMPT for loongson" is updated to patch-2.6.29.1-rt8
Date: Mon, 20 Apr 2009 10:01:55 +0200 [thread overview]
Message-ID: <20090420080155.GA11621@linux-mips.org> (raw)
In-Reply-To: <1240211926.8884.27.camel@falcon>
On Mon, Apr 20, 2009 at 03:18:46PM +0800, Wu Zhangjin wrote:
> On Mon, 2009-04-20 at 13:04 +0800, Zhang Le wrote:
> to Ralf,
>
> I have divided ftrace to several commits in the above git tree, hope you
> can check it, thx :-)
>
> in addition to the static/dynamic/graph function tracer & system call
> tracer implementation, a mips specific ring_buffer_time_stamp
> (kernel/trace/ring_buffer.c) is also implemented to get 1us precision
> time, this is very important to make ftrace available in mips,
> otherwise, we can only get 1ms precision time for the original
> ring_buffer_time_stamp is based on sched_clock(jiffies based).
>
> perhaps we can implement a more precise sched_clock directly, just as
> x86 does(native_sched_clock, tsc based), but in mips, there is only a
> 32bit timer count which will quickly overflow, so it will need an extra
> overflow protection, which may influence the other parts of the kernel.
My git clone is still running to I'm commenting only on the patches you
posted earlier. #ifdef-MIPS'ing things into the generic kernel code
definately won't be an acceptable way to get µs resolution.
Ralf
next prev parent reply other threads:[~2009-04-20 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 2:12 "RT_PREEMPT for loongson" is updated to patch-2.6.29.1-rt8 Wu Zhangjin
2009-04-20 5:04 ` Zhang Le
2009-04-20 7:18 ` Wu Zhangjin
2009-04-20 8:01 ` Ralf Baechle [this message]
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=20090420080155.GA11621@linux-mips.org \
--to=ralf@linux-mips.org \
--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=tglx@linutronix.de \
--cc=wuzhangjin@gmail.com \
--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).