From owner-freebsd-bugs@freebsd.org  Wed Feb 10 21:47:03 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 B9627AA522E
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 10 Feb 2016 21:47:03 +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 AC7D91064
 for <freebsd-bugs@FreeBSD.org>; Wed, 10 Feb 2016 21:47:03 +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 u1ALl3W4018506
 for <freebsd-bugs@FreeBSD.org>; Wed, 10 Feb 2016 21:47:03 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 207068] hwpmc wrap around/sign extension
Date: Wed, 10 Feb 2016 21:47:03 +0000
X-Bugzilla-Reason: AssignedTo
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: joss.upton@yahoo.com
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-8-79zzn3RN4B@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207068-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-207068-8@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-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 21:47:03 -0000

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

--- Comment #5 from joss.upton@yahoo.com ---
(In reply to Konstantin Belousov from comment #4)
I don't know if Sandy Bridge supports the aliases or not.  I do know that
vmware fusion on my Broadwell machine does NOT support the IA32_A_PMCn
registers and thus will panic.

Note you may also need other processes using the PMC to be
scheduled/unscheduled to reproduce... You have to catch a case where it wri=
tes
with EAX[31]=3D1 to IA32_PMCn.  This results in an automatic sign extension=
 (as
described in the Intel arch manual, 18.2.2.3 Full-Width Writes to Performan=
ce
Counter Registers) and ignores EDX completely.

--=20
You are receiving this mail because:
You are the assignee for the bug.=