Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Rob Clark <robdclark@chromium.org>
Cc: Chia-I Wu <olvaffe@gmail.com>,
	freedreno@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	Sean Paul <sean@poorly.run>,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	David Airlie <airlied@linux.ie>,
	Sumit Semwal <sumit.semwal@linaro.org>,
	linux-arm-msm@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH] drm/msm: add trace_dma_fence_emit to msm_gpu_submit
Date: Tue, 26 Apr 2022 18:43:47 +0200	[thread overview]
Message-ID: <a1bcc211-01fa-39b4-8c52-4e0b6143b3a4@amd.com> (raw)
In-Reply-To: <CAJs_Fx6ehFu4Fzvo93XCN+7yufU0NQCshreDniRk37V4f6fmPA@mail.gmail.com>

Sorry for the delayed reply.

Am 12.04.22 um 21:41 schrieb Rob Clark:
> On Sat, Apr 9, 2022 at 7:33 AM Christian König <christian.koenig@amd.com> wrote:
>> Am 08.04.22 um 23:12 schrieb Chia-I Wu:
>>> In practice, trace_dma_fence_init is good enough and almost no driver
>>> calls trace_dma_fence_emit.  But this is still more correct in theory.
>> Well, the reason why basically no driver is calling this is because it
>> is pretty much deprecated.
>>
>> We do have a case in the GPU scheduler where it makes sense to distinct
>> between init and emit, but it doesn't really matter for drivers.
>>
>> So I'm not sure if it's a good idea to add that here.
> visualization can't easily differentiate between drivers/timelines
> where the split matters and ones where it doesn't..  IMO it is better
> to just have the extra trace even in the cases where it comes at the
> same time as the init trace

That's exactly the reason why I want to remove the extra trace.

To make it clear this is only useful for debugging and *NOT* for 
actually visualizing things.

So by adding that here you add more confusion than solving anything.

Regards,
Christian.

>
> BR,
> -R
>
>> Regards,
>> Christian.
>>
>>> Signed-off-by: Chia-I Wu <olvaffe@gmail.com>
>>> Cc: Rob Clark <robdclark@chromium.org>
>>> ---
>>>    drivers/gpu/drm/msm/msm_gpu.c | 2 ++
>>>    1 file changed, 2 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/msm/msm_gpu.c b/drivers/gpu/drm/msm/msm_gpu.c
>>> index faf0c242874e..a82193f41ea2 100644
>>> --- a/drivers/gpu/drm/msm/msm_gpu.c
>>> +++ b/drivers/gpu/drm/msm/msm_gpu.c
>>> @@ -15,6 +15,7 @@
>>>    #include <linux/string_helpers.h>
>>>    #include <linux/devcoredump.h>
>>>    #include <linux/sched/task.h>
>>> +#include <trace/events/dma_fence.h>
>>>
>>>    /*
>>>     * Power Management:
>>> @@ -769,6 +770,7 @@ void msm_gpu_submit(struct msm_gpu *gpu, struct msm_gem_submit *submit)
>>>        gpu->active_submits++;
>>>        mutex_unlock(&gpu->active_lock);
>>>
>>> +     trace_dma_fence_emit(submit->hw_fence);
>>>        gpu->funcs->submit(gpu, submit);
>>>        gpu->cur_ctx_seqno = submit->queue->ctx->seqno;
>>>


      reply	other threads:[~2022-04-26 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 21:12 [PATCH] drm/msm: add trace_dma_fence_emit to msm_gpu_submit Chia-I Wu
2022-04-09  0:06 ` Dmitry Baryshkov
2022-04-09 14:33 ` Christian König
2022-04-09 17:45   ` Chia-I Wu
2022-04-12 19:41   ` Rob Clark
2022-04-26 16:43     ` Christian König [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a1bcc211-01fa-39b4-8c52-4e0b6143b3a4@amd.com \
    --to=christian.koenig@amd.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=olvaffe@gmail.com \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robdclark@chromium.org \
    --cc=sean@poorly.run \
    --cc=sumit.semwal@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox