From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751385AbWJHUwG (ORCPT ); Sun, 8 Oct 2006 16:52:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751389AbWJHUwG (ORCPT ); Sun, 8 Oct 2006 16:52:06 -0400 Received: from www.osadl.org ([213.239.205.134]:18879 "EHLO mail.tglx.de") by vger.kernel.org with ESMTP id S1751385AbWJHUwD (ORCPT ); Sun, 8 Oct 2006 16:52:03 -0400 Subject: Re: + clocksource-increase-initcall-priority.patch added to -mm tree From: Thomas Gleixner Reply-To: tglx@linutronix.de To: Daniel Walker Cc: akpm@osdl.org, johnstul@us.ibm.com, mingo@elte.hu, zippel@linux-m68k.org, LKML In-Reply-To: <1160339986.3693.135.camel@c-67-180-230-165.hsd1.ca.comcast.net> References: <200610070153.k971ren4020838@shell0.pdx.osdl.net> <1160294812.22911.8.camel@localhost.localdomain> <1160302797.22911.37.camel@localhost.localdomain> <1160319033.3693.19.camel@c-67-180-230-165.hsd1.ca.comcast.net> <1160319234.5686.12.camel@localhost.localdomain> <1160322317.3693.47.camel@c-67-180-230-165.hsd1.ca.comcast.net> <1160323127.5686.37.camel@localhost.localdomain> <1160324288.3693.71.camel@c-67-180-230-165.hsd1.ca.comcast.net> <1160326363.5686.48.camel@localhost.localdomain> <1160327879.3693.97.camel@c-67-180-230-165.hsd1.ca.comcast.net> <1160334205.5686.72.camel@localhost.localdomain> <1160339986.3693.135.camel@c-67-180-230-165.hsd1.ca.comcast.net> Content-Type: text/plain Date: Sun, 08 Oct 2006 22:52:02 +0200 Message-Id: <1160340722.5686.85.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2006-10-08 at 13:39 -0700, Daniel Walker wrote: > > The reason why this was delayed into late boot is simply that the > > unstable, unsynchronized TSC's made way too much trouble and the pmtimer > > can not be initialized early. > > > > I'm not going to accept that. Your change might work on 5 machines you > > have tested on, but we start over with the same breakage we solved > > already. > > Your going to have to explain the breakage further. I don't recall > seeing any discussion on this. See above, but I'm happy to copy it. > > The reason why this was delayed into late boot is simply that the > > unstable, unsynchronized TSC's made way too much trouble and the pmtimer > > can not be initialized early. I don't have the bug reports handy, but they are in the LKML archives. > > This early boot instrumentation code can work with low resolution time > > information quite well and none of the boot code does need any high res > > time information. Boot code is different from a running system and has > > different requirements. > > > > This is a solution for a nonexisting problem, which just brings back > > already solved ones. > > There is at least one existing problem which it does solve. Which one exactly? I'm not aware of a problem with the existing code at all. > How about we > discuss the early TSC boot breakage, which you mention above, so I can > properly fix this situation. See above. Also it interferes probably with the highres/dyntick code, as we might switch over way too early. Have not looked into that yet. tglx