On 2014.03.28 10:21:50 -0700, bradley.d.vol...@intel.com wrote:
From: Brad Volkin bradley.d.vol...@intel.com
There is some thought that the data from the performance counters enabled
via OACONTROL should only be available to the process that enabled counting.
To limit snooping, require that
On Thu, Apr 10, 2014 at 02:07:21PM +0800, Zhenyu Wang wrote:
On 2014.03.28 10:21:50 -0700, bradley.d.vol...@intel.com wrote:
From: Brad Volkin bradley.d.vol...@intel.com
There is some thought that the data from the performance counters enabled
via OACONTROL should only be available to
On 2014.04.10 08:43:40 +0200, Daniel Vetter wrote:
At least in the case of mesa you _must_ use mesa (or whatever your gl
library is) to insert the MI_PERF cmd at just the rigth spots in the
command stream and ofc flush all outstanding vertices and similar things.
If you want a global perf
On Fri, 28 Mar 2014, bradley.d.vol...@intel.com wrote:
From: Brad Volkin bradley.d.vol...@intel.com
There is some thought that the data from the performance counters enabled
via OACONTROL should only be available to the process that enabled counting.
To limit snooping, require that any batch
From: Brad Volkin bradley.d.vol...@intel.com
There is some thought that the data from the performance counters enabled
via OACONTROL should only be available to the process that enabled counting.
To limit snooping, require that any batch buffer which sets OACONTROL to a
non-zero value also sets
On 03/28/2014 10:21 AM, bradley.d.vol...@intel.com wrote:
From: Brad Volkin bradley.d.vol...@intel.com
There is some thought that the data from the performance counters enabled
via OACONTROL should only be available to the process that enabled counting.
To limit snooping, require that any
