Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030472AbVIPRZF (ORCPT ); Fri, 16 Sep 2005 13:25:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030590AbVIPRZF (ORCPT ); Fri, 16 Sep 2005 13:25:05 -0400 Received: from [139.30.44.2] ([139.30.44.2]:18180 "EHLO gans.physik3.uni-rostock.de") by vger.kernel.org with ESMTP id S1030472AbVIPRZC (ORCPT ); Fri, 16 Sep 2005 13:25:02 -0400 Date: Fri, 16 Sep 2005 19:25:00 +0200 (CEST) From: Tim Schmielau To: Tim Bird cc: jesper.juhl@gmail.com, "Randy.Dunlap" , linux-kernel@vger.kernel.org Subject: Re: early printk timings way off In-Reply-To: Message-ID: References: <9a87484905091515495f435db7@mail.gmail.com> <432AFB01.3050809@am.sony.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1084 Lines: 27 On Fri, 16 Sep 2005, Tim Schmielau wrote: > So, one jump (probably the first) happens when time_init sets use_tsc. > Do we understand the other jump as well? OK, looking at the numbers we have just one time-jump: > [4294667.296000] CPU 0 irqstacks, hard=c03d2000 soft=c03d1000 > [4294667.296000] PID hash table entries: 2048 (order: 11, 32768 bytes) > [ 0.000000] Detected 1400.279 MHz processor. > [ 27.121583] Using tsc for high-res timesource > [ 27.121620] Console: colour dummy device 80x25 > [ 27.122909] Dentry cache hash table entries: 131072 (order: 7, 524288 The "Detected 1400.279 MHz processor." line just happens to be written _during_ time_init, when use_tsc is already set, but cycles_2_ns is not yet initialized. So I think everything is well-understood. It's just a matter of whether it's worth fixing. Tim - 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/