From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754978AbYIFVIU (ORCPT ); Sat, 6 Sep 2008 17:08:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752873AbYIFVIJ (ORCPT ); Sat, 6 Sep 2008 17:08:09 -0400 Received: from www.tglx.de ([62.245.132.106]:34987 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752854AbYIFVII (ORCPT ); Sat, 6 Sep 2008 17:08:08 -0400 Date: Sat, 6 Sep 2008 23:07:50 +0200 (CEST) From: Thomas Gleixner To: Linus Torvalds cc: Alok Kataria , Alan Cox , LKML , Arjan van de Veen , "H. Peter Anvin" , Peter Zijlstra , Dan Hecht , Garrett Smith Subject: Re: [RFC patch 0/4] TSC calibration improvements In-Reply-To: Message-ID: References: <20080904160036.GA18382@elte.hu> <20080904190728.59634020@lxorguk.ukuu.org.uk> <20080904204305.GA29065@elte.hu> <1220653095.14401.72.camel@alok-dev1> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 6 Sep 2008, Linus Torvalds wrote: > On Sat, 6 Sep 2008, Thomas Gleixner wrote: > > > > If Alok has the second check in place and is actually worried about > > that 288us impact, then we can add the following (untested), which > > does not impact the speed of the check. > > Guys, please. > > Show some _taste_. Tell the hardware dudes who made that crap so difficult > Dammit, stop adding random crap to "native_calibrate_tsc()" and make it > look like total and utter SHIT. > > If you want to do that > > tsc1 = tsc_read_refs(&ref1, hpet); > .. > tsc2 = tsc_read_refs(&ref1, hpet); > > around calibration and comparing it, then do it *once*. Do it over the > whole thing. Do it in a function of its own, instead of making this > horrible and unreadable mess. Over which _whole_ thing ? You want to have the very very fast thing, which is not reliable under all circumstances as Alok pointed out and I merily added a sanity check around that for testing. > This patch may be fine as a "let's check if it works" thing, but please > don't send out total SH*T to public lists. Why not ? We want to figure out if it solves the problem and sending it to public lists is the fastest way to get it tested. > Some _tasted_ in programming, please! What we apply finally is a totally different thing. Thanks, tglx