From: Sven-Thorsten Dietrich <thebigcorporation@gmail.com>
To: Eric W Anderson <Eric.Anderson@Colorado.EDU>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: At a loss: Kernel 2.6.19-rt15 with ixp425
Date: Tue, 08 Jun 2010 11:37:12 -0700 [thread overview]
Message-ID: <1276022232.9420.17.camel@sven.thebigcorporation.com> (raw)
In-Reply-To: <20100608181752.GA19521@colorado.edu>
On Tue, 2010-06-08 at 12:17 -0600, Eric W Anderson wrote:
> Hello All,
Hi Eric,
2.6.19 is very very old.
What is preventing you from a Kernel upgrade?
Sven
>
> I can't figure out (or haven't figured out) how to get actual high-resolution
> timers on the above platform. I'm kind of stuck with 2.6.19, unfortunately.
> I've applied the -rt patch to stock 2.6.19, merged in some random patches to
> support my hardware, and gotten it to boot. But, here's what confuses me: I
> have the hrtimer API, but my actual clock resolution is still shown as 10ms.
>
> root@patty:/# cat /proc/timer_list
> Timer List Version: v0.1
> HRTIMER_MAX_CLOCK_BASES: 2
> now at 2766685920305 nsecs
>
> cpu: 0
> clock 0:
> .index: 0
> .resolution: 10000000 nsecs
> .get_time: ktime_get_real
> active timers:
> clock 1:
> .index: 1
> .resolution: 10000000 nsecs
> .get_time: ktime_get
> active timers:
> #0: <c4615ec8>, hrtimer_wakeup
> # expires at 2766802147358 nsecs [in 116227053 nsecs]
> #1: <c4615ec8>, it_real_fn
> # expires at 2767494816966 nsecs [in 808896661 nsecs]
> #2: <c4615ec8>, it_real_fn
> # expires at 3642163204498 nsecs [in 875477284193 nsecs]
> #3: <c4615ec8>, it_real_fn
> # expires at 3643403169278 nsecs [in 876717248973 nsecs]
>
> Additionally, I don't see CONFIG_HIGH_RES_TIMERS anywhere in my kernel
> menuconfig. I've added a patch from Kevin Hilman and Milan Svoboda
> (http://lkml.indiana.edu/hypermail/linux/kernel/0607.1/2343.html) which
> purports to enable a high-resolution clock event source for this board, but
> that doesn't seem to change anything.
>
> I think I don't properly understand the preempt_rt / hrtimers /
> board-specific-bits ecosystem here. What are the bits and pieces I need in
> order to have high-resolution timers on this platform?
>
> Many, many thanks,
> Eric Anderson
>
>
next prev parent reply other threads:[~2010-06-08 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 18:17 At a loss: Kernel 2.6.19-rt15 with ixp425 Eric W Anderson
2010-06-08 18:37 ` Sven-Thorsten Dietrich [this message]
2010-06-08 19:32 ` Eric W Anderson
2010-06-09 17:02 ` Sven-Thorsten Dietrich
2010-06-09 18:50 ` Xianghua Xiao
2010-06-10 2:25 ` Sven-Thorsten Dietrich
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=1276022232.9420.17.camel@sven.thebigcorporation.com \
--to=thebigcorporation@gmail.com \
--cc=Eric.Anderson@Colorado.EDU \
--cc=linux-rt-users@vger.kernel.org \
/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).