Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751103AbVK3HjW (ORCPT ); Wed, 30 Nov 2005 02:39:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751104AbVK3HjW (ORCPT ); Wed, 30 Nov 2005 02:39:22 -0500 Received: from tayrelbas03.tay.hp.com ([161.114.80.246]:39582 "EHLO tayrelbas03.tay.hp.com") by vger.kernel.org with ESMTP id S1751103AbVK3HjV (ORCPT ); Wed, 30 Nov 2005 02:39:21 -0500 Date: Tue, 29 Nov 2005 23:38:31 -0800 From: Stephane Eranian To: Nicholas Miell Cc: Andi Kleen , Ray Bryant , discuss@x86-64.org, linux-kernel@vger.kernel.org, perfctr-devel@lists.sourceforge.net Subject: Re: [Perfctr-devel] Re: Enabling RDPMC in user space by default Message-ID: <20051130073831.GB7521@frankl.hpl.hp.com> Reply-To: eranian@hpl.hp.com References: <200511291056.32455.raybry@mpdtxmail.amd.com> <20051129180903.GB6611@frankl.hpl.hp.com> <20051129181344.GN19515@wotan.suse.de> <1133300591.3271.1.camel@entropy> <20051129215207.GR19515@wotan.suse.de> <1133303615.3271.12.camel@entropy> <20051129224346.GS19515@wotan.suse.de> <1133305338.3271.30.camel@entropy> <20051129231750.GU19515@wotan.suse.de> <1133306966.3271.36.camel@entropy> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1133306966.3271.36.camel@entropy> User-Agent: Mutt/1.4.1i Organisation: HP Labs Palo Alto Address: HP Labs, 1U-17, 1501 Page Mill road, Palo Alto, CA 94304, USA. E-mail: eranian@hpl.hp.com Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1543 Lines: 33 Nicholas, On Tue, Nov 29, 2005 at 03:29:26PM -0800, Nicholas Miell wrote: > On Wed, 2005-11-30 at 00:17 +0100, Andi Kleen wrote: > > On Tue, Nov 29, 2005 at 03:02:18PM -0800, Nicholas Miell wrote: > > > On Tue, 2005-11-29 at 23:43 +0100, Andi Kleen wrote: > > > > To give an bad analogy RDTSC usage in the last years is > > > > like explicit spinning wait loops for delays in the earlier > > > > times. They tended to work on some subset of computers, > > > > but were always bad and caused problems and people eventually learned > > > > it was better to use operating system services for this. > > > > > > And you are now suggesting people should use RDPMC instead of OS > > > services? > > > > For any kind of timers they should use the OS service > > (gettimeofday/clock_gettime). The OS will go to extraordinary > > means to make it as fast as possible, but when it's slow > > then because it's not possible to do it faster accurately > > (that's the case right now modulo one possible optimization) > > > > For cycle counting where they previously used RDTSC they should > > use RDPMC 0 now. > > Well, if that's all you want them to use RDPMC 0 for, why not just make > PMCs programmable from userspace? > Simply because write a PERFSEL (i.e. an MSR) register is a privileged operation. - 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/