From owner-freebsd-performance@FreeBSD.ORG  Tue Sep 27 22:36:08 2011
Return-Path: <owner-freebsd-performance@FreeBSD.ORG>
Delivered-To: freebsd-performance@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B22A01065670
	for <freebsd-performance@freebsd.org>;
	Tue, 27 Sep 2011 22:36:08 +0000 (UTC) (envelope-from gnn@freebsd.org)
Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176])
	by mx1.freebsd.org (Postfix) with ESMTP id 827F38FC0A
	for <freebsd-performance@freebsd.org>;
	Tue, 27 Sep 2011 22:36:08 +0000 (UTC)
Received: from [209.249.190.124] (helo=gnnmac.hudson-trading.com)
	by vps.hungerhost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69)
	(envelope-from <gnn@freebsd.org>)
	id 1R8fS7-0006fQ-Hn; Tue, 27 Sep 2011 17:44:35 -0400
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=us-ascii
From: George Neville-Neil <gnn@freebsd.org>
In-Reply-To: <j5btru$rg0$1@dough.gmane.org>
Date: Tue, 27 Sep 2011 17:44:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BE45FDD-1A7A-4F9D-B32B-30D19C897112@freebsd.org>
References: <j5ae29$e6g$1@dough.gmane.org> <j5asv4$p7e$1@dough.gmane.org>
	<CAJ-Vmo=m079Dko-erfSdWZaX6nqjxrTVt1U8P0kOK27g5kD8Bw@mail.gmail.com>
	<j5btru$rg0$1@dough.gmane.org>
To: Anton Yuzhaninov <citrin@citrin.ru>
X-Mailer: Apple Mail (2.1244.3)
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - vps.hungerhost.com
X-AntiAbuse: Original Domain - freebsd.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - freebsd.org
Cc: freebsd-performance@freebsd.org
Subject: Re: hwpmc overflow
X-BeenThere: freebsd-performance@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Performance/tuning <freebsd-performance.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-performance>,
	<mailto:freebsd-performance-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-performance>
List-Post: <mailto:freebsd-performance@freebsd.org>
List-Help: <mailto:freebsd-performance-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-performance>,
	<mailto:freebsd-performance-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2011 22:36:08 -0000


On Sep 21, 2011, at 01:48 , Anton Yuzhaninov wrote:

> On Wed, 21 Sep 2011 09:27:33 +0800, Adrian Chadd wrote:
> AC> Is this an AMD class CPU?
> AC>=20
> AC> The way the counters work on some platforms is that they count =
_up_ to
> AC> an overflow value, trigger the overflow interrupt, and PMC then is
> AC> supposed to calculate what the original value was.
> AC> It sounds like maybe that isn't working correctly for a certain =
class
> AC> of counters?
>=20
> CPU: Intel(R) Xeon(R) CPU E5645 @ 2.40GHz
>=20

If you count them individually do you still get the overflows?  That is, =
if you run
the same workload but only count instructions, then run it again with =
the next counter,
etc.  I am wondering if something is wrong because of the number of =
things you're trying
to count at the same time.

Best,
George