From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/4569] _stp_gettimeofday_ns doesn't work for some archs
Date: Tue, 20 Nov 2012 22:00:00 -0000 [thread overview]
Message-ID: <bug-4569-6586-PbkjbIshgj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-4569-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=4569
--- Comment #1 from William Cohen <wcohen at redhat dot com> 2012-11-20 22:00:16 UTC ---
It appears that some recent changes in the 3.6 linux kernel provide something
other than 0 for get_cycles():
http://lxr.linux.no/#linux+v3.6/arch/arm/include/asm/timex.h
#ifdef ARCH_HAS_READ_CURRENT_TIMER
#define get_cycles() ({ cycles_t c; read_current_timer(&c) ? 0 : c; })
#else
#define get_cycles() (0)
#endif
In theory this should allow allow gtod and OVERLOAD2 test to work. The Fedora
arm 18 kernel should have the correct CONF* set, but with the Linux wecf18arm
3.6.3-3.fc18.armv7hl.tegra still seeing:
FAIL: gtod (0)
FAIL: OVERLOAD2 no expected error
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next parent reply other threads:[~2012-11-20 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-4569-6586@http.sourceware.org/bugzilla/>
2012-11-20 22:00 ` wcohen at redhat dot com [this message]
2012-11-20 22:40 ` jistone at redhat dot com
2007-05-30 14:29 [Bug runtime/4569] New: " hunt at redhat dot com
2007-06-07 15:00 ` [Bug runtime/4569] " hunt 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=bug-4569-6586-PbkjbIshgj@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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).