From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761924AbYEHLIR (ORCPT ); Thu, 8 May 2008 07:08:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753668AbYEHLH7 (ORCPT ); Thu, 8 May 2008 07:07:59 -0400 Received: from mail.gmx.net ([213.165.64.20]:39774 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753152AbYEHLH6 (ORCPT ); Thu, 8 May 2008 07:07:58 -0400 X-Authenticated: #34473864 X-Provags-ID: V01U2FsdGVkX1/SRNJ9EGjSrER82jhB/PEbMQxH4IZPbjqOvhDH55 xYLrXg8k46Bini Message-ID: <4822DF0B.8080109@gmx.de> Date: Thu, 08 May 2008 13:07:55 +0200 From: Philipp Kohlbecher User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Thomas Gleixner CC: linux-kernel@vger.kernel.org, John Stultz Subject: Re: clocksources: order of preference References: <4822D8B6.4090008@gmx.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thomas Gleixner wrote: > We also check the TSC with a watchdog mechanism, which verifies that > is is keeping accurate time. When we detect that TSC does not, we > replace it by the next available clock source. > True. In all the cases I know, the watchdog mechanism worked and marked the TSC as unstable. The soft lockup only led to a (sometimes considerable) delay at boot time. > You may submit one, but it's very unlikely that is gets applied. :) > Makes sense. :) Thank you for your extremely quick reply! - Philipp Kohlbecher