Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1946511AbWKJL4w (ORCPT ); Fri, 10 Nov 2006 06:56:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1946513AbWKJL4w (ORCPT ); Fri, 10 Nov 2006 06:56:52 -0500 Received: from mail.suse.de ([195.135.220.2]:58516 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1946512AbWKJL4v (ORCPT ); Fri, 10 Nov 2006 06:56:51 -0500 From: Andi Kleen To: Ingo Molnar Subject: Re: [patch 13/19] GTOD: Mark TSC unusable for highres timers Date: Fri, 10 Nov 2006 12:56:35 +0100 User-Agent: KMail/1.9.5 Cc: Pavel Machek , Andrew Morton , tglx@linutronix.de, john stultz , LKML , Len Brown , Arjan van de Ven , Roman Zippel References: <20061109233030.915859000@cruncher.tec.linutronix.de> <20061110111231.GB3291@elf.ucw.cz> <20061110114806.GA6780@elte.hu> In-Reply-To: <20061110114806.GA6780@elte.hu> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200611101256.35306.ak@suse.de> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 713 Lines: 17 > we could, but it would have to be almost empty right now :-) Reason: > even on systems that have (hardware-initialized) 'perfect' TSCs and > which do not support any frequency scaling or power-saving mode, our > current TSC initialization on SMP systems introduces a small (1-2 usecs) > skew. On Intel we don't sync the TSC anymore and on most systems users seem to be happy at least. And on multicore AMD it is drifting anyways and usually turned off. -Andi - 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/