Subject: Re: [patch 13/19] GTOD: Mark TSC unusable for highres timers
From: Thomas Gleixner <tglx@linutronix.de>
Reply-To: tglx@linutronix.de
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
       john stultz <johnstul@us.ibm.com>, LKML <linux-kernel@vger.kernel.org>,
       Len Brown <lenb@kernel.org>, Arjan van de Ven <arjan@infradead.org>,
       Roman Zippel <zippel@linux-m68k.org>
In-Reply-To: <200611111459.05854.ak@suse.de>
References: <20061109233030.915859000@cruncher.tec.linutronix.de>
	 <200611111451.33511.ak@suse.de>
	 <1163253488.8335.247.camel@localhost.localdomain>
	 <200611111459.05854.ak@suse.de>
Content-Type: text/plain
Date: Sat, 11 Nov 2006 15:08:52 +0100
Message-Id: <1163254132.8335.251.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 983
Lines: 29

On Sat, 2006-11-11 at 14:59 +0100, Andi Kleen wrote:
> On Saturday 11 November 2006 14:58, Thomas Gleixner wrote:
> 
> > > 
> > > > > My guess is that some of the checks in there are just broken and need
> > > > > to be fixed.
> > > > 
> > > > It's the unconditional mark_unstable call in ACPI C2 state. /me looks.
> > > 
> > > The system doesn't support C2 states. It's an older single socket Athlon 64 
> > > with VIA chipset. I haven't looked in detail on why it fails.
> > 
> > Does it have cpu freqency changing ?
> 
> Yep. But only OS controlled one (powernow).
> 
> Most likely it happens when ondemand starts doing its thing.

Yes, thats one of the criterias the tsc clocksource is using. I'm
looking into that right now.

	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/