public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* RE: probe hrtimer testing
@ 2006-05-24 20:51 Stone, Joshua I
  2006-05-24 22:01 ` Roland McGrath
  0 siblings, 1 reply; 6+ messages in thread
From: Stone, Joshua I @ 2006-05-24 20:51 UTC (permalink / raw)
  To: William Cohen; +Cc: systemtap

On Wednesday, May 24, 2006 12:05 PM, William Cohen wrote:
> In the 2.6.17-rc4 kernel it looks like hrtimer is used by
> kernel/itimer.c. Is there a particular benefit explicitly using the
> hrtimer rather than going through the normal timer mechanism? Are
> there other modules that could use the hrtimer directly?

My understanding is that itimers are intended for user-mode processes.
They operate by sending a SIGALRM on expiration, which I don't think we
can use.

The advantage of hrtimers is just the potential for better resolution.
The normal timer mechanism is specified in terms of jiffies.  Currently
hrtimers are also jiffy limited, but since they are specified in
nanoseconds, there's the potential that future arch-specific
implementations will provide accuracy greater than the jiffy rate.

Whether sub-jiffy timers are useful for SystemTap is open for
discussion...


Josh

^ permalink raw reply	[flat|nested] 6+ messages in thread
* RE: probe hrtimer testing
@ 2006-05-23 18:34 Stone, Joshua I
  2006-05-24 15:36 ` Frank Ch. Eigler
  2006-05-24 19:04 ` William Cohen
  0 siblings, 2 replies; 6+ messages in thread
From: Stone, Joshua I @ 2006-05-23 18:34 UTC (permalink / raw)
  To: William Cohen, systemtap

On Tuesday, May 23, 2006 10:57 AM, William Cohen wrote:
> Looking over the test coverage results recently posted, one of the
> places that is lacking in testing is the probes for hrtimer. Josh,
> does anyone have some tests for that area of the translator? It would
> do a lot to improve the test coverage of tapsets.cxx.

The hrtimer is not tested because it's not complete.  I ran into a
problem with needing exported symbols from the kernel, and LKML rejected
my request.  So until support is added to the kernel ABI for using
hrtimers, the code I added will be unusable.

I checked it in as part of normal development, in hopes that the ABI
would get resolved.  Since hrtimers are still not exported, perhaps I
should remove the code.  Would it be sufficient for your coverage tests
if I just blocked out the code with "#ifdef ENABLE_HRTIMER"?

If anyone has an interest in seeing the hrtimers work in SystemTap,
please speak up.  If there's enough interest, then maybe we can go back
to LKML to try to get it enabled in the ABI.


Josh

^ permalink raw reply	[flat|nested] 6+ messages in thread
* probe hrtimer testing
@ 2006-05-23 17:58 William Cohen
  0 siblings, 0 replies; 6+ messages in thread
From: William Cohen @ 2006-05-23 17:58 UTC (permalink / raw)
  To: systemtap

Looking over the test coverage results recently posted, one of the 
places that is lacking in testing is the probes for hrtimer. Josh, does 
anyone have some tests for that area of the translator? It would do a 
lot to improve the test coverage of tapsets.cxx.

http://people.redhat.com/wcohen/stap-combined-tests-20060518/src/index.html


-Will

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2006-05-24 22:01 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-05-24 20:51 probe hrtimer testing Stone, Joshua I
2006-05-24 22:01 ` Roland McGrath
  -- strict thread matches above, loose matches on Subject: below --
2006-05-23 18:34 Stone, Joshua I
2006-05-24 15:36 ` Frank Ch. Eigler
2006-05-24 19:04 ` William Cohen
2006-05-23 17:58 William Cohen

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).