From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/10493] New: runtime/time.c: need autoconf for cpu_khz
Date: Thu, 06 Aug 2009 22:26:00 -0000 [thread overview]
Message-ID: <20090806222624.10493.fche@redhat.com> (raw)
Some kernels (old rhel4 x86-64 xen) don't have and/or export cpu_khz.
These would need to go back to the heuristic estimation code in
runtime/time.c:__stp_get_freq().
--
Summary: runtime/time.c: need autoconf for cpu_khz
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10493
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-08-06 22:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 22:26 fche at redhat dot com [this message]
2009-08-07 9:42 ` [Bug runtime/10493] " wenji dot huang at oracle dot com
2009-08-07 18:04 ` fche at redhat dot com
2010-01-12 9:18 ` wenji dot huang at oracle dot com
2010-01-13 3:35 ` wenji dot huang at oracle dot com
2010-02-26 2:23 ` fche 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=20090806222624.10493.fche@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).