From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Helge Deller <deller@gmx.de>
Cc: Joel Soete <soete.joel@tiscali.be>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] sched_clock implementation
Date: Sun, 21 Sep 2003 10:24:58 -0400 [thread overview]
Message-ID: <20030921142458.GE6963@systemhalted> (raw)
In-Reply-To: <200309211320.36485.deller@gmx.de>
On Sun, Sep 21, 2003 at 01:20:36PM +0200, Helge Deller wrote:
> On Sunday 21 September 2003 02:04, Grant Grundler wrote:
> > On Sat, Sep 20, 2003 at 06:02:10PM +0000, Joel Soete wrote:
> > > a quick look into paxx.pdf which about CR16 speak of "peak instruction
> > > rate" but do not define anywhere?
> > > I presume that is the cpu clock but would like somebody confirm.
> >
> > Read about "Interval Timer" (cr16) in the PA 2.0 Arch book.
> > PDC provides the exact rate that CR16 is changing.
> > Looks like PDC_TOD_ITIMER is the call but I'm not sure offhand.
> > In any case, I've only seen it used as CPU cycle counter.
> > (ie 1:1 with CPU clock).
>
> Hi Joel,
>
> I think we have the rate in the variable "boot_cpu_data.cpu_hz" (see
> arch/parisc/kernel/processor.c) already.
Technically that's our highest precision timer :)
c.
next prev parent reply other threads:[~2003-09-21 14:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 20:35 [parisc-linux] sched_clock implementation Matthew Wilcox
2003-09-19 15:32 ` Joel Soete
2003-09-19 16:00 ` Carlos O'Donell
2003-09-19 16:11 ` Joel Soete
2003-09-20 18:02 ` Joel Soete
2003-09-21 0:04 ` Grant Grundler
2003-09-21 11:20 ` Helge Deller
2003-09-21 14:24 ` Carlos O'Donell [this message]
2003-10-05 15:43 ` Joel Soete
2003-10-06 14:20 ` Carlos O'Donell
[not found] ` <3F5CB6FB0000DCF3@ocpmta1.freegates.net>
2003-10-06 17:31 ` Carlos O'Donell
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=20030921142458.GE6963@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=deller@gmx.de \
--cc=parisc-linux@parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.