All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Jonas Diemer <diemer@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA 686 timer bugfix incomplete
Date: Thu, 8 Nov 2001 22:22:36 +0100	[thread overview]
Message-ID: <20011108222236.A6581@suse.cz> (raw)
In-Reply-To: <20011107211445.A2286@suse.cz> <Pine.LNX.4.05.10111080917140.19515-100000@marina.lowendale.com.au> <20011108090215.G3708@suse.cz> <20011108102124.31ca040f.diemer@gmx.de> <20011108210840.A6266@suse.cz> <20011108221751.5273484e.diemer@gmx.de>
In-Reply-To: <20011108221751.5273484e.diemer@gmx.de>; from diemer@gmx.de on Thu, Nov 08, 2001 at 10:17:51PM +0100

On Thu, Nov 08, 2001 at 10:17:51PM +0100, Jonas Diemer wrote:

> On Thu, 8 Nov 2001 21:08:40 +0100
> Vojtech Pavlik <vojtech@suse.cz> wrote:
> 
> > There is a little problem with RTC, though:
> > 
> > While you can set it up to generate interrupts at say 1024 Hz, you can't
> > read any value of how much time passed since last interrupt. You can do
> > this on the PIT (i8253), and this is the part that is buggy.
> > 
> > TSC is perfect, precise and accurate, but not reliable in long term.
> > Some CPUs do thermal throttling, notebooks play with CPU speed, etc,
> > etc. And it's not synchronized to any interrupt source.
> > 
> > Ugly, ugly, ugly is the PC architecture.
> > 
> 
> can't you just read the battery buffered clock? how are other OSes such as
> Window$ doing the timing?

You can. But you only get 0.5 second resolution, which obviously isn't
good enough for microsecond timing.

-- 
Vojtech Pavlik
SuSE Labs

  parent reply	other threads:[~2001-11-08 21:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-07 11:50 VIA 686 timer bugfix incomplete Jonas Diemer
2001-11-07 12:15 ` Alan Cox
2001-11-07 19:25   ` Vojtech Pavlik
2001-11-07 19:48     ` Jonas Diemer
2001-11-07 20:14       ` Vojtech Pavlik
2001-11-07 22:32         ` Neale Banks
2001-11-08  8:02           ` Vojtech Pavlik
2001-11-08  9:21             ` Jonas Diemer
2001-11-08 20:08               ` Vojtech Pavlik
     [not found]                 ` <20011108221751.5273484e.diemer@gmx.de>
2001-11-08 21:22                   ` Vojtech Pavlik [this message]
2001-11-08 21:30                 ` george anzinger
2001-11-08 23:30                   ` Alan Cox
2001-11-09  8:34                     ` Vojtech Pavlik
2001-11-09 17:21                     ` george anzinger
2001-11-07 19:29   ` Steve Underwood
2001-11-08 20:11     ` Vojtech Pavlik
2001-11-09  2:57       ` Steve Underwood
  -- strict thread matches above, loose matches on Subject: below --
2001-11-09 19:19 Grover, Andrew

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=20011108222236.A6581@suse.cz \
    --to=vojtech@suse.cz \
    --cc=diemer@gmx.de \
    --cc=linux-kernel@vger.kernel.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 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.