Le mercredi 04 janvier 2006 à 17:49 +0100, Jan Kiszka a écrit :
> Stelian Pop wrote:
> > Hi,
> > 
> 88> I'm trying to use the xeno_timerbench as a replacement to the old 2.0
> > klatency module and I encounter some problems.
> > 
> > This is on my in-progress ARM Xenomai port. User space latency and old
> > klatency work great (my board has some hardware latency problems though
> > - latencies can be as high as 500 us..). This in on a 2.6.14.5 kernel
> > using the latest ipipe patch and the latest SVN trunk xenomai.
> > 
> > Note that I never used the RTDM skin until now, so the problem could be
> > as well in the core RTDM code.
> 
> Almost impossible - there are no bugs! ;)

there is no spoon either :)

 
> Well, seriously, I don't believe it's a RTDM-related issue as the
> invocation of the timer-handler and the kernel-task tests are quite
> similar. The former works, the latter fails inside the scheduler, this
> rather indicates some issue in the arch-specific part of the scheduler
> (the timer test runs in IRQ-context).
> 
> Did you test some RTDM or native kernel-only timed-task before? With
> RTDM this can be as trivial as this one:

As I said in the previous post, the old klatency works.

As for your rtdm example:

# insmod test-rtdm.ko
test_rtdm: module license 'unspecified' taints kernel.
# I'm alive.I'm alive.I'm alive.I'm alive.I'm alive.I'm alive.I'm
alive.I'm alive.I'm alive.I'm alive.I'm alive.I'm alive.I'm alive.I'm
alive.I'm alive.I'm alive.

seems to work fine too (and I'm even able to rmmod the module).

Stelian.
-- 
Stelian Pop <[EMAIL PROTECTED]>


Reply via email to