From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/11209] New: Provide an alternative time tapset
Date: Thu, 21 Jan 2010 22:36:00 -0000 [thread overview]
Message-ID: <20100121223614.11209.jistone@redhat.com> (raw)
For most scripts, I think the Epoch time provided by gettimeofday_s() is not
that relevant. Most of the time, all that's needed are relative times from one
event to another, and any time source should be fine.
I suggest creating a new walltime tapset that uses whatever time source is most
convenient/efficient. On newer kernels, an implementation backed by the
kernel's cpu_clock() may be a good choice. Where no better option exists, we
can always fall back to gettimeofday automatically.
--
Summary: Provide an alternative time tapset
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: tapsets
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: jistone at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=11209
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2010-01-21 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 22:36 jistone at redhat dot com [this message]
2010-01-26 17:12 ` [Bug tapsets/11209] " fche at redhat dot com
2010-01-26 22:55 ` jistone at redhat 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=20100121223614.11209.jistone@redhat.com \
--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).