linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: paubert <paubert@iram.es>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	Davide Libenzi <davidel@xmailserver.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: how to measure scheduler latency on powerpc?  realfeel doesn't work due to /dev/rtc issues
Date: Fri, 9 May 2003 11:37:29 +0000	[thread overview]
Message-ID: <20030509113729.C16311@mrt-lx16.iram.es> (raw)
In-Reply-To: <3EBB4735.30701@nortelnetworks.com>

On Fri, May 09, 2003 at 02:14:13AM -0400, Chris Friesen wrote:
> William Lee Irwin III wrote:
> 
> >Try the timebase instead.
> 
> The timestamp is not hard to get.  The problem is getting a medium-frequency 
> 
> (2KHz or so) hardware interrupt to drive the test.

Reload the decrementer with a smaller value, and read the decrementer value
at the beginning of every timer_interrupt. Timekeeping only depends on the
timebase on PPC (I wrote most of the code), taking additional decrementer
interrupts does not harm. Actually the simplest and most efficient way
to perform a self IPI on PPC is to write 0 to the decrementer (2 machine
instructions). 

Actually, a way to measure the longest time during which interrupts are masked
would be:

	- when disabling interrupts, set decrementer to zero if they
	were previously enabled.
	- read the decrementer on every timer/external interrupt,
	if the value is negative and too large print the value
	and the point at which the interrupts were reenabled.

That's not perfect (it will generate not too many false positives but
quite some overhead, but it should work).

	Gabriel 

  parent reply	other threads:[~2003-05-09 11:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 22:12 how to measure scheduler latency on powerpc? realfeel doesn't work due to /dev/rtc issues Chris Friesen
2003-05-09  0:13 ` William Lee Irwin III
2003-05-09  0:38   ` Davide Libenzi
2003-05-09  0:38     ` William Lee Irwin III
2003-05-09  0:56       ` Richard B. Johnson
2003-05-09  3:52         ` Chris Friesen
2003-05-09  4:13           ` Roland Dreier
2003-05-09  6:07             ` Chris Friesen
2003-05-09  4:26           ` William Lee Irwin III
2003-05-09  6:14             ` Chris Friesen
2003-05-09  6:20               ` William Lee Irwin III
2003-05-09  6:53                 ` Chris Friesen
2003-05-09  7:01                   ` William Lee Irwin III
2003-05-09 16:47                     ` Robert Love
2003-05-09 16:53                       ` William Lee Irwin III
2003-05-09 17:38                         ` Chris Friesen
2003-05-09 11:37               ` paubert [this message]
2003-05-09  8:23             ` mikpe
2003-05-09  8:17 ` how to measure scheduler latency on powerpc? realfeel doesn Giuliano Pochini
2003-05-10  0:39 how to measure scheduler latency on powerpc? realfeel doesn' t work due to /dev/rtc issues Perez-Gonzalez, Inaky
2003-05-12 23:55 ` William Lee Irwin III
     [not found] <493798056@toto.iv>
2003-05-12  5:04 ` how to measure scheduler latency on powerpc? realfeel doesn't " Peter Chubb
2003-05-12  5:08   ` William Lee Irwin III
2003-05-13  0:20 how to measure scheduler latency on powerpc? realfeel doesn' t " Perez-Gonzalez, Inaky
2003-05-13  1:02 ` William Lee Irwin III
2003-05-13  2:08 Perez-Gonzalez, Inaky

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=20030509113729.C16311@mrt-lx16.iram.es \
    --to=paubert@iram.es \
    --cc=cfriesen@nortelnetworks.com \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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 NNTP newsgroup(s).