From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/3916] improve timing monotony
Date: Wed, 24 Jan 2007 19:32:00 -0000 [thread overview]
Message-ID: <20070124193224.20288.qmail@sourceware.org> (raw)
In-Reply-To: <20070124160955.3916.fche@redhat.com>
------- Additional Comments From fche at redhat dot com 2007-01-24 19:32 -------
(In reply to comment #1)
> Possible solutions:
> * Find a better estimate of the cpu freq
> * Use a clock that's independent of cpu freq (e.g., a motherboard/chipset timer)
> * Get the kernel to provide a lockless gettimeofday
> * Others?
One simple thing is to keep the per-cpu counts from ever decreasing during
the resynchronization phase. This could let them drift ahead of real time,
but so be it. If it gets too bad, the runtime could emit a warning.
Also, the resync phase may not be necessary so frequently on stable_tsc
processors.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=3916
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-01-24 19:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 16:10 [Bug runtime/3916] New: " fche at redhat dot com
2007-01-24 18:52 ` [Bug runtime/3916] " joshua dot i dot stone at intel dot com
2007-01-24 19:13 ` joshua dot i dot stone at intel dot com
2007-01-24 19:32 ` fche at redhat dot com [this message]
2007-06-07 2:15 ` joshua dot i dot stone at intel dot com
2007-08-15 9:10 ` mhiramat at redhat dot com
2007-08-15 15:11 ` mhiramat at redhat dot com
2007-08-16 18:17 ` joshua dot i dot stone at intel dot com
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=20070124193224.20288.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).