Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Aug 2013 20:27:16 GMT
From:      adrian chadd <adrian@FreeBSD.org>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   misc/181346: [hwpmc] Sandy Bridge Xeon - workaround required for some perf events
Message-ID:  <201308162027.r7GKRGtV097848@oldred.freebsd.org>
Resent-Message-ID: <201308162030.r7GKU0Sl095315@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         181346
>Category:       misc
>Synopsis:       [hwpmc] Sandy Bridge Xeon - workaround required for some perf events
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 16 20:30:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     adrian chadd
>Release:        
>Organization:
>Environment:
>Description:
There's a workaround required for some events on Sandy bridge Xeon hardware.

http://software.intel.com/en-us/articles/performance-monitoring-on-intel-xeon-processor-e5-family

Here's the workaround packaged up in a linux-specific python script. ugh.

https://github.com/andikleen/pmu-tools/blob/master/latego.py

I have no idea about the specifics of the workaround; only that we should likely add support to hwpmc to do this.

>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201308162027.r7GKRGtV097848>