Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760697AbYJITpf (ORCPT ); Thu, 9 Oct 2008 15:45:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754690AbYJITp1 (ORCPT ); Thu, 9 Oct 2008 15:45:27 -0400 Received: from kara.rubysoft.com ([64.34.171.174]:52798 "EHLO kara.rubysoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753770AbYJITp0 (ORCPT ); Thu, 9 Oct 2008 15:45:26 -0400 Date: Thu, 9 Oct 2008 13:45:20 -0600 (MDT) From: Jeff Hansen X-X-Sender: ninkid@ren Reply-To: Jeff Hansen To: Thomas Gleixner cc: Chris Snook , torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, mingo@elte.hu Subject: Re: [PATCH] Re: x86_32 tsc/pit and hrtimers In-Reply-To: Message-ID: References: <48ECFEDC.90305@redhat.com> <48ED1728.5060708@redhat.com> <48ED2A89.3000902@redhat.com> <48EE4FC4.7070902@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 822 Lines: 28 OK, so are we all agreed that something like clocksource_trust=tsc would be the best? -Jeff --------------------------------------------------- "If someone's gotta do it, it might as well be me." On Thu, 9 Oct 2008, Thomas Gleixner wrote: > On Thu, 9 Oct 2008, Chris Snook wrote: >> >> Fair enough, but do you think it's worthwhile to have an option to disable >> CLOCK_SOURCE_MUST_VERIFY checking for all timers, or should we implement this >> on a case-by-case basis when there's legitimate cause, like with TSC? > > Case-by-case is preferred. > > Thanks, > > tglx > > -- 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/