On 12/5/2017 7:52 PM, Lionel Landwerlin wrote:
On 15/11/17 12:13, Sagar Arun Kamble wrote:
From: Sourab Gupta
Currently, we have the ability to only forward the GPU timestamps in the
samples (which are generated via OA reports). This limits the ability to
correlate these samples with the sys
On 15/11/17 12:13, Sagar Arun Kamble wrote:
From: Sourab Gupta
Currently, we have the ability to only forward the GPU timestamps in the
samples (which are generated via OA reports). This limits the ability to
correlate these samples with the system events.
An ability is therefore needed to rep
On 11/15/2017 6:01 PM, Chris Wilson wrote:
Quoting Sagar Arun Kamble (2017-11-15 12:13:54)
From: Sourab Gupta
Currently, we have the ability to only forward the GPU timestamps in the
samples (which are generated via OA reports). This limits the ability to
correlate these samples with the sys
On 11/15/2017 5:43 PM, Sagar Arun Kamble wrote:
From: Sourab Gupta
Currently, we have the ability to only forward the GPU timestamps in the
samples (which are generated via OA reports). This limits the ability to
correlate these samples with the system events.
An ability is therefore needed
Quoting Sagar Arun Kamble (2017-11-15 12:13:54)
> From: Sourab Gupta
>
> Currently, we have the ability to only forward the GPU timestamps in the
> samples (which are generated via OA reports). This limits the ability to
> correlate these samples with the system events.
>
> An ability is therefo
From: Sourab Gupta
Currently, we have the ability to only forward the GPU timestamps in the
samples (which are generated via OA reports). This limits the ability to
correlate these samples with the system events.
An ability is therefore needed to report timestamps in different clock
domains, suc
