Gilles Chanteperdrix wrote:
> Hi,
> here comes, for review, a patch which reduces the overhead of
> clock_gettime by directly reading the tsc in user-space for
> architectures that support it.

Highly welcome. But I have one concern: How and when do you propagate
wallclock_offset changes to user space?

I think we need some vsyscall-alike approach for this, some read-only
page that is mapped into every RT process, containing things like a
regularly updated offset (seqlock fashioned) or other read-only
information (shadow mode? cpu id?).


Attachment: signature.asc
Description: OpenPGP digital signature

Xenomai-core mailing list

Reply via email to