Date: Thu, 9 Oct 2008 19:20:09 +0200
From: Pavel Machek <pavel@suse.cz>
To: Chris Snook <csnook@redhat.com>
Cc: Jeff Hansen <x@jeffhansen.com>, torvalds@linux-foundation.org,
       linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: x86_32 tsc/pit and hrtimers
Message-ID: <20081009172009.GD1370@ucw.cz>
References: <Pine.LNX.4.64.0810071640110.25661@ren> <48ECFEDC.90305@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48ECFEDC.90305@redhat.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1124
Lines: 24

Hi!

>> Can you please tell me if this is supposed to work, and I just have a
>> poorly configured kernel; or if TSC/PIT drivers were not designed to work
>> this way in the first place.  If it wasn't designed to do this, do you
>> have any tips on implementing this, since I'll be needing to do that?
>>
> This is not supposed to work, but it might be worthwhile to add a boot 
> option to force the kernel to trust the TSC, as hardware that lacks any 
> high-res timers also tends to be primitive enough that the TSC can be 
> trusted, if it exists.  If you patch out the CLOCK_SOURCE_MUST_VERIFY 
> flag on the TSC, do you get correctly-functioning high-res timers on this 
> system?

Untrue. Unstable tsc dates back to pentium MMX times.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/