From: "Christian König" <ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Shirish S <shirish.s-5C7GfCeVMHo@public.gmane.org>,
Alexander.Deucher-5C7GfCeVMHo@public.gmane.org
Cc: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/amdgpu: skip IB tests for KIQ in general
Date: Thu, 4 Oct 2018 09:11:56 +0200 [thread overview]
Message-ID: <3d8d4c0a-1a87-a4c4-fee6-da62d6069899@gmail.com> (raw)
In-Reply-To: <1538579711-19601-1-git-send-email-shirish.s-5C7GfCeVMHo@public.gmane.org>
Am 03.10.2018 um 17:15 schrieb Shirish S:
> From: Pratik Vishwakarma <Pratik.Vishwakarma@amd.com>
>
> [Why]
> 1. We never submit IBs to KIQ.
> 2. Ring test pass without KIQ's ring also.
> 3. By skipping we see an improvement of around 500ms
> in the amdgpu's resume time.
>
> [How]
> skip IB tests for KIQ ring type.
>
> Signed-off-by: Shirish S <shirish.s@amd.com>
> Signed-off-by: Pratik Vishwakarma <Pratik.Vishwakarma@amd.com>
Well I'm not sure if that is a good idea or not.
On the one hand it is true that we never submit IBs to the KIQ, so
testing that doesn't make much sense actually.
But on the other hand the 500ms delay during resume points out a problem
with the KIQ, e.g. interrupts are not working correctly!
Question is now if we should ignore that problem because we never use
interrupts on the KIQ?
If the answer is to keep it as it is we should remove the intterupt
handling for the KIQ as well.
Otherwise I would say we should fix interrupts on the KIQ and then we
also don't need this change any more.
Regards,
Christian.
> ---
>
> This patch is a follow-up to the suggestion given by Alex,
> while reviewing the patch: https://patchwork.freedesktop.org/patch/250912/
>
> -Shirish S
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c
> index 47817e0..b8963b7 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_ib.c
> @@ -354,6 +354,14 @@ int amdgpu_ib_ring_tests(struct amdgpu_device *adev)
> if (!ring || !ring->ready)
> continue;
>
> + /* skip IB tests for KIQ in general for the below reasons:
> + * 1. We never submit IBs to the KIQ
> + * 2. KIQ doesn't use the EOP interrupts,
> + * we use some other CP interrupt.
> + */
> + if (ring->funcs->type == AMDGPU_RING_TYPE_KIQ)
> + continue;
> +
> /* MM engine need more time */
> if (ring->funcs->type == AMDGPU_RING_TYPE_UVD ||
> ring->funcs->type == AMDGPU_RING_TYPE_VCE ||
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-10-04 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 15:15 [PATCH] drm/amdgpu: skip IB tests for KIQ in general Shirish S
[not found] ` <1538579711-19601-1-git-send-email-shirish.s-5C7GfCeVMHo@public.gmane.org>
2018-10-04 3:51 ` Alex Deucher
2018-10-04 7:11 ` Christian König [this message]
[not found] ` <3d8d4c0a-1a87-a4c4-fee6-da62d6069899-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-10-05 5:57 ` S, Shirish
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=3d8d4c0a-1a87-a4c4-fee6-da62d6069899@gmail.com \
--to=ckoenig.leichtzumerken-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
--cc=shirish.s-5C7GfCeVMHo@public.gmane.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