On Fri, Nov 23, 2018 at 1:13 PM Koenig, Christian
wrote:
> Am 23.11.18 um 18:36 schrieb Eric Anholt:
> > Christian König writes:
> >> Am 20.11.18 um 21:57 schrieb Eric Anholt:
> >>> Kenny Ho writes:
> Account for the number of command submitted to amdgpu by type on a per
> cgroup basi
Am 23.11.18 um 18:36 schrieb Eric Anholt:
> Christian König writes:
>
>> Am 20.11.18 um 21:57 schrieb Eric Anholt:
>>> Kenny Ho writes:
>>>
Account for the number of command submitted to amdgpu by type on a per
cgroup basis, for the purpose of profiling/monitoring applications.
>>> For
Christian König writes:
> Am 20.11.18 um 21:57 schrieb Eric Anholt:
>> Kenny Ho writes:
>>
>>> Account for the number of command submitted to amdgpu by type on a per
>>> cgroup basis, for the purpose of profiling/monitoring applications.
>> For profiling other drivers, I've used perf tracepoints
Am 20.11.18 um 21:57 schrieb Eric Anholt:
Kenny Ho writes:
Account for the number of command submitted to amdgpu by type on a per
cgroup basis, for the purpose of profiling/monitoring applications.
For profiling other drivers, I've used perf tracepoints, which let you
get useful timelines of
Am 20.11.18 um 19:58 schrieb Kenny Ho:
Account for the number of command submitted to amdgpu by type on a per
cgroup basis, for the purpose of profiling/monitoring applications.
x prefix in the control file name x.cmd_submitted.amd.stat signify
experimental.
Change-Id: Ibc22e5bda600f54fe820fe0a
Kenny Ho writes:
> Account for the number of command submitted to amdgpu by type on a per
> cgroup basis, for the purpose of profiling/monitoring applications.
For profiling other drivers, I've used perf tracepoints, which let you
get useful timelines of multiple events in the driver. Have you
