after Philippe tried hard to shrink my queue, I was at least able to add
one new major patch:

Trying to write down the docs for rtdm_timer I realised that we really
need to do something about this scenario: multiple skins on different
time bases are exchanging time stamps directly or indirectly (e.g. via
RTDM devices). So far, those time stamps would be hopelessly out of sync
and could easily break things.

The answer I found is to synchronise all time bases as good as possible.
That means if one base changes its wall clock offset, all others need to
be adjusted as well. At this chance, we would also implement
synchronisation of the time bases on the system clock when they get
started. Because skins may work with different type width to represent
time, relative changes have to be applied, i.e. the core API changes
from xntbase_set_time(new_time) to xntbase_adjust_time(relative_change).
The patch (global-wallclock.patch) finally touches more parts than I was
first hoping. Here is the full list:

 - synchronise slave time bases on the master on xntbase_start
 - xntbase_set_time -> xntbase_adjust_time, fixing all time bases
   currently registered
 - make xnarch_start_timer return the nanos since the last host tick
   (only ia64 affected, all others return 0 anyway, causing one tick
   off when synchronising on system time -- but this fiddling becomes
   pointless on the long term due to better clocksourses on all archs)
 - adapt vrtx, vxworks, and psos+ skin to new scheme, fixing sc_sclock
   at this chance
 - make xnarch_get_sys_time internal, no skin should (need to) touch
   this anymore

The patch is lightly tested and appears to meet its goals. However, the
changes are fundamental and need careful review.

Other changes in the current stack:
 - configure link test for sched_setaffinity (see earlier posting)
 - kill svctable from the pod structure
 - updated ltt patch

Please check



Attachment: signature.asc
Description: OpenPGP digital signature

Xenomai-core mailing list

Reply via email to