From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270772AbTHFSDv (ORCPT ); Wed, 6 Aug 2003 14:03:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270813AbTHFSDv (ORCPT ); Wed, 6 Aug 2003 14:03:51 -0400 Received: from kinesis.swishmail.com ([209.10.110.86]:24337 "HELO kinesis.swishmail.com") by vger.kernel.org with SMTP id S270772AbTHFSDu (ORCPT ); Wed, 6 Aug 2003 14:03:50 -0400 Message-ID: <3F314603.7050907@techsource.com> Date: Wed, 06 Aug 2003 14:16:35 -0400 From: Timothy Miller User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tim Schmielau CC: Patrick Moor , lkml , george anzinger Subject: Re: time jumps (again) References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Is there any way the kernel could detect clock problems like drift and jumps by comparing the effects of different timers? And when a problem is detected, it can correct the situation automatically. How many interrupt timers are there in various systems? How much can we rely on the accuracy of each one?