Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265222AbUJVTxl (ORCPT ); Fri, 22 Oct 2004 15:53:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267553AbUJVTtz (ORCPT ); Fri, 22 Oct 2004 15:49:55 -0400 Received: from viper.oldcity.dca.net ([216.158.38.4]:32923 "HELO viper.oldcity.dca.net") by vger.kernel.org with SMTP id S265222AbUJVTrA (ORCPT ); Fri, 22 Oct 2004 15:47:00 -0400 Subject: Re: How is user space notified of CPU speed changes? From: Lee Revell To: Chris Friesen Cc: Alan Cox , Linux Kernel Mailing List , Robert Love In-Reply-To: <4179623C.9050807@nortelnetworks.com> References: <1098399709.4131.23.camel@krustophenia.net> <1098444170.19459.7.camel@localhost.localdomain> <1098468316.5580.18.camel@krustophenia.net> <4179623C.9050807@nortelnetworks.com> Content-Type: text/plain Message-Id: <1098474416.5580.52.camel@krustophenia.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 22 Oct 2004 15:46:57 -0400 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 819 Lines: 22 On Fri, 2004-10-22 at 15:40, Chris Friesen wrote: > Lee Revell wrote: > > > Seems like you are implying that any userspace app that needs to know > > the CPU speed is broken. Is this correct? > > No, we're saying that Intel's tsc implementation is broken. > > x86 really could use an on-die register that increments at 1GHz independent of > clock speed and is synchronized across all CPUs in an SMP box. Well, it looks like we can just fix JACK to not use the TSC for timing. Seems like the current design is fundamentally incompatible with CPU scaling. Lee - 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/