This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/21305] clock_gettime(CLOCK_MONOTONIC_RAW) can and should use rdtsc instructions instead of entering kernel through VDSO
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 24 Mar 2017 19:53:06 +0000
- Subject: [Bug libc/21305] clock_gettime(CLOCK_MONOTONIC_RAW) can and should use rdtsc instructions instead of entering kernel through VDSO
- Auto-submitted: auto-generated
- References: <bug-21305-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21305
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #6 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Jason Vas Dias from comment #5)
> So now I need to know : will a future version of glibc
> ever consider providing an interface to rdtscp in user-space
> for such platforms as my machine ?
I think you should propose a kernel patch which adds CLOCK_MONOTONIC_RAW
support first. I doubt that for architectures which can use CPU clocks with
constant rates, there is a need for locking for CLOCK_MONOTONIC_RAW. But Intel
engineers can probably help with that.
I don't think we will change glibc in the way you suggest because the vDSO data
structures appear to be kernel implementation details. And there is the issue
that glibc should not have to know about specific TSC properties.
--
You are receiving this mail because:
You are on the CC list for the bug.