Jan Kiszka wrote:
 > > Sometimes the result is "Should be near 84000: 100000", that is kind of 
 > > correct, since the tickval is 100000, although I think that those 
 > > functions 
 > > in the RTDM driver context should be independent of the tick value set by 
 > > the 
 > > user program... Maybe using oneshot in the driver calls and periodic in 
 > > the 
 > > application... I really don't know what would be the best approach here...
 > rtdm_clock_read always uses the nucleus clock. Using something different
 > (e.g. always TSC) would break applications specifying absolute times
 > derived from the return values of other skins' functions.

Maybe adding a service to RTDM would allow users to measure short time
intervals with RTDM using the TSC ?

The native (rt_timer_tsc()) and posix (clock_gettime(CLOCK_MONOTONIC))
skins have a way to do this.


                                            Gilles Chanteperdrix.

Xenomai-core mailing list

Reply via email to