All of lore.kernel.org
 help / color / mirror / Atom feed
From: "zhenyu.ren" <zhenyu.ren@aliyun.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Jesper Derehag <jderehag@hotmail.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: 答复: clock_gettime vdso issue
Date: Fri, 27 Mar 2015 08:57:43 +0800	[thread overview]
Message-ID: <b11ab443-45d9-43ab-bde7-27524cf91b74__43143.3209371336$1427417953$gmane$org@aliyun.com> (raw)
In-Reply-To: 1722941338.111044.1427387596544.JavaMail.zimbra@efficios.com


[-- Attachment #1.1: Type: text/plain, Size: 2533 bytes --]

Hello  Are there any documents about what the clock override feature is? It seems that the feature will hurt time resolution,doesn't it?In fact,I will try to get the symbol addr of  __vdso_clock_gettime just like the same way glibc does with __vdso_gettimeofday.Is there any other cheaper way to call    __vdso_clock_gettime  ?
Thankszhenyu.ren
------------------------------------------------------------------发件人:Mathieu Desnoyers <mathieu.desnoyers@efficios.com>发送时间:2015年3月27日(星期五) 00:33收件人:Jesper Derehag <jderehag@hotmail.com>抄 送:zhenyu.ren <zhenyu.ren@aliyun.com>,lttng-dev <lttng-dev@lists.lttng.org>主 题:Re: [lttng-dev] clock_gettime vdso issue
Yes, the clock override feature, as well as the getcpu override,
should be merged within lttng-ust and lttng-tools master branches
this week. Stay tuned!

Thanks,

Mathieu

----- Original Message -----
> 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?
> 
> /Jesper
> 
> ________________________________
> > Date: Thu, 26 Mar 2015 15:25:49 +0800
> > From: zhenyu.ren@aliyun.com
> > To: lttng-dev@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@lists.lttng.org
> > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>  		 	   		  
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> 

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

[-- Attachment #1.2: Type: text/html, Size: 8211 bytes --]

[-- Attachment #2: Type: text/plain, Size: 155 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  parent reply	other threads:[~2015-03-27  0:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cf147ee4-5d02-423f-a352-672a739809d4@aliyun.com>
2015-03-26  7:54 ` clock_gettime vdso issue Jesper Derehag
     [not found] ` <DUB123-W38081C479AED1FCAFCDED3DD080@phx.gbl>
2015-03-26 16:33   ` Mathieu Desnoyers
2015-03-27  0:57   ` zhenyu.ren [this message]
     [not found]   ` <", 1722941338.111044.1427387596544.JavaMail.zimbra"@efficios.com>
     [not found]     ` <b11ab443-45d9-43ab-bde7-27524cf91b74@aliyun.com>
2015-03-27 19:57       ` 答复: " Mathieu Desnoyers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='b11ab443-45d9-43ab-bde7-27524cf91b74__43143.3209371336$1427417953$gmane$org@aliyun.com' \
    --to=zhenyu.ren@aliyun.com \
    --cc=jderehag@hotmail.com \
    --cc=lttng-dev@lists.lttng.org \
    --cc=mathieu.desnoyers@efficios.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.