From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266328AbUGAWUx (ORCPT ); Thu, 1 Jul 2004 18:20:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266334AbUGAWUx (ORCPT ); Thu, 1 Jul 2004 18:20:53 -0400 Received: from 64.221.211.203.ptr.us.xo.net ([64.221.211.203]:39366 "EHLO mail.pathscale.com") by vger.kernel.org with ESMTP id S266328AbUGAWT4 (ORCPT ); Thu, 1 Jul 2004 18:19:56 -0400 Subject: Re: perfctr questions From: "Bryan O'Sullivan" To: bert hubert Cc: Mikael.Pettersson@csd.uu.se, linux-kernel@vger.kernel.org In-Reply-To: <20040701220448.GA16515@outpost.ds9a.nl> References: <20040701220448.GA16515@outpost.ds9a.nl> Content-Type: multipart/mixed; boundary="=-YvHcg308Xj2kWFu8e8oR" Date: Thu, 01 Jul 2004 15:19:54 -0700 Message-Id: <1088720394.32000.26.camel@serpentine.internal.keyresearch.com> Mime-Version: 1.0 X-Mailer: Evolution 1.5.9.1 (1.5.9.1-2) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org --=-YvHcg308Xj2kWFu8e8oR Content-Type: text/plain Content-Transfer-Encoding: 7bit On Fri, 2004-07-02 at 00:04 +0200, bert hubert wrote: > I'm trying to test your performance counters stuff, but I can't get it to do > anything remotely useful! Probably just me. No, it's just obscure. You have three options for now. The first is to read the Intel or AMD CPU performance counter docs, which I don't recommend, because that kind of thing is never fun. The second is to build a library called PAPI, which includes a command called papiex that provides a less intimidating performance counter interface. However, building PAPI with a not-quite-the-same version of perfctr is a bit daunting, so I don't recommend that, either. Your third option is to build a version of perfex that I've hacked on, but not had time to finish up and submit to Mikael. I've attached it as a tarball. This includes a man page that makes the usage less scary, and it also accepts (gasp) textual arguments instead of hex strings. I've tested it on P6, Pentium M and AMD64 chips.