From owner-freebsd-amd64@freebsd.org  Thu Feb 11 13:57:35 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41BE9AA4FD2
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Thu, 11 Feb 2016 13:57:35 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 33BC599B
 for <freebsd-amd64@FreeBSD.org>; Thu, 11 Feb 2016 13:57:35 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u1BDvY1a072072
 for <freebsd-amd64@FreeBSD.org>; Thu, 11 Feb 2016 13:57:35 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 207068] hwpmc wrap around/sign extension
Date: Thu, 11 Feb 2016 13:57:35 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-STABLE
X-Bugzilla-Keywords: hwpmc
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-207068-6-3CnUgnYrQX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207068-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-207068-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 11 Feb 2016 14:33:01 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2016 13:57:35 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207068

--- Comment #7 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to joss.upton from comment #6)
I believe that the behaviour of reading MSR 0xc1 is architectural ?  Anyway=
, on
sandybridge:

sandy% sudo cpucontrol -m 0xc1=3D0x80000000 /dev/cpuctl0
sandy% sudo cpucontrol -m 0xc1 /dev/cpuctl0
MSR 0xc1: 0x0000ffff 0x80000000

SB does have full-width PMC write capability:
sandy% sudo cpucontrol -m 0x345 /dev/cpuctl0
MSR 0x345: 0x00000000 0x000031c3
bit 13 (FW_WRITE) is set

But my concern is that I cannot reproduce the issue with the following scri=
pt:
for x in $(jot 8); do pmcstat -P CPU_CLK_UNHALTED_CORE perl ./loop.pl
2>/dev/null &; done

Unpatched kernel must exhibit the problem because it does not write to PMC
through aliases and all writes are clipped.  I want to be able to reproduce
this before commit, at least I need to validate the change and to understand
that it is complete (I agree that this is the right approach, at least).

--=20
You are receiving this mail because:
You are on the CC list for the bug.=