linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: Gabriel Paubert <paubert@iram.es>,
	linuxppc-dev@lists.linuxppc.org, Samuel Rydh <samuel@ibrium.se>
Subject: Re: [PATCH] gettimeofday stability
Date: Mon, 16 Apr 2001 18:19:39 -0400	[thread overview]
Message-ID: <3ADB6FFB.C40B3574@mvista.com> (raw)
In-Reply-To: 20010416160035.777CF2F0D3@apollo.valhalla.net


Iain Sandoe wrote:
>
> > I still object strongly to anything touching the timebase, however.
>
> I'd prefer if it wasn't touched too...

As I recall, "touching" the TB simply means reading it and computing
elapsed ticks since the last read.  I don't remember anything changing
the value in the timebase registers (which isn't possible outside
of the kernel).

I regularly use the TB for user application event timing, and
haven't seen anything abnormal (other than the code I was testing :-).


	-- Dan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-04-16 22:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-16 16:00 [PATCH] gettimeofday stability Iain Sandoe
2001-04-16 22:19 ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-11 19:00 Samuel Rydh
2001-04-11 19:42 ` Gabriel Paubert
2001-04-11 20:09   ` Karim Yaghmour
2001-04-11 21:31     ` Benjamin Herrenschmidt
2001-04-12 18:09     ` Gabriel Paubert
2001-04-14  6:49       ` Karim Yaghmour
2001-04-16 11:56         ` Gabriel Paubert
2001-04-16 13:25           ` Benjamin Herrenschmidt
2001-04-16 12:53             ` Gabriel Paubert
2001-04-17 11:22     ` Gabriel Paubert
2001-04-11 23:07   ` Samuel Rydh
2001-04-16 11:25     ` Gabriel Paubert
2001-04-19 20:43       ` Samuel Rydh
2001-04-21 15:21         ` Gabriel Paubert
2001-04-21 18:16           ` Samuel Rydh
2001-04-21 19:37             ` Gabriel Paubert

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=3ADB6FFB.C40B3574@mvista.com \
    --to=dan@mvista.com \
    --cc=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    --cc=samuel@ibrium.se \
    /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).