This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/14438] New: clock_gettime CLOCK_THREAD_CPUTIME_ID doesn't delegate to vsyscall
- From: "arun at sharma-home dot net" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Mon, 06 Aug 2012 19:03:06 +0000
- Subject: [Bug libc/14438] New: clock_gettime CLOCK_THREAD_CPUTIME_ID doesn't delegate to vsyscall
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14438
Bug #: 14438
Summary: clock_gettime CLOCK_THREAD_CPUTIME_ID doesn't delegate
to vsyscall
Product: glibc
Version: 2.17
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: unassigned@sourceware.org
ReportedBy: arun@sharma-home.net
CC: drepper.fsp@gmail.com
Classification: Unclassified
Created attachment 6566
--> http://sourceware.org/bugzilla/attachment.cgi?id=6566
clock_gettime() makes syscalls, but __vdso_clock_gettime doesn't.
clock_gettime(CLOCK_THREAD_CPUTIME_ID, &ts) seems to always make a syscall,
even on kernels that provide a vdso. Although upstream kernels don't have the
patches we're running with, I find this behavior surprising.
Why doesn't glibc always call __vdso_clock_gettime() and let the kernel decide
on the best implementation regardless of the clock id?
Relevant patches:
http://thread.gmane.org/gmane.linux.kernel/1231015/focus=1231016
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.