Wolfgang Mauerer wrote:
Some points that may require further discussion:
- POSIX only specifies a few clock_ids, and these have already been
extended by the Linux kernel. We use the maximum id (16) for the new
clock, but it might also make sense to use 7 (CLOCK_MONOTONIC_COARSE+1)
or
Gilles Chanteperdrix wrote:
Wolfgang Mauerer wrote:
Gilles Chanteperdrix wrote:
Wolfgang Mauerer wrote:
This update_vsyscall code would call ipipe_dispatch_event to pass the
data to Xenomai.
okay. That seems to have dropped from my radar, as I don't recall having
any issues with this
Gilles Chanteperdrix wrote:
Wolfgang Mauerer wrote:
Some points that may require further discussion:
- POSIX only specifies a few clock_ids, and these have already been
extended by the Linux kernel. We use the maximum id (16) for the new
clock, but it might also make sense to use 7
Wolfgang Mauerer wrote:
(This is the Xenomai part of the mechanism, please see the ipipe
mailing list for the patches that provide the required basis
infrastructure)
This patch series extends Xenomai with a new clock, CLOCK_HOST_REALTIME.
It allows for sharing NTP-corrected real time
Gilles Chanteperdrix wrote:
Wolfgang Mauerer wrote:
(This is the Xenomai part of the mechanism, please see the ipipe
mailing list for the patches that provide the required basis
infrastructure)
This patch series extends Xenomai with a new clock, CLOCK_HOST_REALTIME.
It allows for sharing
