From: "Christian König" <christian.koenig@amd.com>
To: Chia-I Wu <olvaffe@gmail.com>, freedreno@lists.freedesktop.org
Cc: 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>,
Rob Clark <robdclark@chromium.org>
Subject: Re: [PATCH] drm/msm: add trace_dma_fence_emit to msm_gpu_submit
Date: Sat, 9 Apr 2022 16:33:16 +0200 [thread overview]
Message-ID: <fe1e583c-b942-0f33-55d1-435f0966b110@amd.com> (raw)
In-Reply-To: <20220408211230.601475-1-olvaffe@gmail.com>
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.
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;
>
next prev parent reply other threads:[~2022-04-09 14:33 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 [this message]
2022-04-09 17:45 ` Chia-I Wu
2022-04-12 19:41 ` Rob Clark
2022-04-26 16:43 ` Christian König
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=fe1e583c-b942-0f33-55d1-435f0966b110@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