[lttng-dev] clock_gettime vdso issue

Jesper Derehag jderehag at hotmail.com
Thu Mar 26 03:54:26 EDT 2015

There has been discussions regarding adding capability to override the clock implementation.

If that support is arriving, you could always write your own (say a separate thread reading clock periodically and storing in a cache, then your own clock implementation could get that cached timestamp).
Obviously you would need to think very carefully about clock resolution and frequency for your clock thread, but it should from a performance point of view be big improvement..

Maybe Mathieu(?) could shed some light on the clock override?


> Date: Thu, 26 Mar 2015 15:25:49 +0800 
> From: zhenyu.ren at aliyun.com 
> To: lttng-dev at lists.lttng.org 
> Subject: [lttng-dev] clock_gettime vdso issue 
> Hi,Team 
> You may not feel how painful I am with a too old GLIBC which does 
> NOT support vdso clock_gettime. Especially in ust case, 
> trace_clock_read will call clock_gettime to record the time of every 
> event. 
> Does anyone know how to avoid system_call clock_gettime with this old GLIBC?? 
> Thanks in advance 
> zhenyu.ren 
> _______________________________________________ lttng-dev mailing list 
> lttng-dev at lists.lttng.org 
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev 

More information about the lttng-dev mailing list