Applied to drm-misc-next.
Regards,
Qiang
On Wed, Mar 18, 2020 at 5:11 AM Vasily Khoruzhick wrote:
>
> On Mon, Mar 16, 2020 at 6:41 PM Qiang Yu wrote:
>
> > Not concrete reason, as the comment, trace point when
> > dma_fence_signal act as the task completion event, so not add duplicate
> > one.
On Mon, Mar 16, 2020 at 6:41 PM Qiang Yu wrote:
> Not concrete reason, as the comment, trace point when
> dma_fence_signal act as the task completion event, so not add duplicate
> one.
I see. Patch is:
Reviewed-by: Vasily Khoruzhick
Regards,
Vasily
On Sun, Mar 15, 2020 at 12:36 PM Vasily Khoruzhick wrote:
>
> On Sat, Mar 7, 2020 at 5:55 AM Qiang Yu wrote:
> >
> > track lima task start which can be combined with
> > dma_fence_signal to identify task execution time.
> >
> > example command to record:
> >
> > trace-cmd record -i \
> > -e "li
On Sat, Mar 7, 2020 at 5:55 AM Qiang Yu wrote:
>
> track lima task start which can be combined with
> dma_fence_signal to identify task execution time.
>
> example command to record:
>
> trace-cmd record -i \
> -e "lima:lima_task_submit" -e "lima:lima_task_run" \
> -e "*fence:*fence_signaled"
track lima task start which can be combined with
dma_fence_signal to identify task execution time.
example command to record:
trace-cmd record -i \
-e "lima:lima_task_submit" -e "lima:lima_task_run" \
-e "*fence:*fence_signaled" -e "drm:drm_vblank_event" \
-e "drm:drm_vblank_event_queued" s
