From: "Christian König" <ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Andrey Grodzovsky
<andrey.grodzovsky-5C7GfCeVMHo@public.gmane.org>,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
tomeu-XCtybt49RKsYaV1qd6yewg@public.gmane.org,
eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org
Subject: Re: [PATCH] drm/v3d: Fix calling drm_sched_resubmit_jobs for same sched.
Date: Wed, 13 Mar 2019 09:25:32 +0100 [thread overview]
Message-ID: <31336cff-8e16-7879-8f63-609de7f83150@gmail.com> (raw)
In-Reply-To: <1552409822-17230-1-git-send-email-andrey.grodzovsky-5C7GfCeVMHo@public.gmane.org>
Am 12.03.19 um 17:57 schrieb Andrey Grodzovsky:
> Also stop calling drm_sched_increase_karma multiple times.
>
> Signed-off-by: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
Acked-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/v3d/v3d_sched.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/v3d/v3d_sched.c b/drivers/gpu/drm/v3d/v3d_sched.c
> index 4704b2d..ce7c737b 100644
> --- a/drivers/gpu/drm/v3d/v3d_sched.c
> +++ b/drivers/gpu/drm/v3d/v3d_sched.c
> @@ -231,20 +231,17 @@ v3d_gpu_reset_for_timeout(struct v3d_dev *v3d, struct drm_sched_job *sched_job)
> mutex_lock(&v3d->reset_lock);
>
> /* block scheduler */
> - for (q = 0; q < V3D_MAX_QUEUES; q++) {
> - struct drm_gpu_scheduler *sched = &v3d->queue[q].sched;
> -
> - drm_sched_stop(sched);
> + for (q = 0; q < V3D_MAX_QUEUES; q++)
> + drm_sched_stop(&v3d->queue[q].sched);
>
> - if(sched_job)
> - drm_sched_increase_karma(sched_job);
> - }
> + if(sched_job)
> + drm_sched_increase_karma(sched_job);
>
> /* get the GPU back into the init state */
> v3d_reset(v3d);
>
> for (q = 0; q < V3D_MAX_QUEUES; q++)
> - drm_sched_resubmit_jobs(sched_job->sched);
> + drm_sched_resubmit_jobs(&v3d->queue[q].sched);
>
> /* Unblock schedulers and restart their jobs. */
> for (q = 0; q < V3D_MAX_QUEUES; q++) {
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2019-03-13 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 16:57 [PATCH] drm/v3d: Fix calling drm_sched_resubmit_jobs for same sched Andrey Grodzovsky
[not found] ` <1552409822-17230-1-git-send-email-andrey.grodzovsky-5C7GfCeVMHo@public.gmane.org>
2019-03-12 17:33 ` Eric Anholt
[not found] ` <87imworo9v.fsf-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
2019-03-12 17:48 ` Grodzovsky, Andrey
[not found] ` <CY4PR12MB1446C0DAFA3349227DEB9B0AEA490-rpdhrqHFk070Y0OdeIqGUgdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-03-13 16:13 ` Eric Anholt
[not found] ` <87lg1ioipw.fsf-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
2019-03-13 16:36 ` Grodzovsky, Andrey
[not found] ` <fc067a25-260f-d056-f22c-10d9aac7a612-5C7GfCeVMHo@public.gmane.org>
2019-03-13 17:53 ` Eric Anholt
2019-03-13 18:49 ` Grodzovsky, Andrey
2019-03-13 8:25 ` 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=31336cff-8e16-7879-8f63-609de7f83150@gmail.com \
--to=ckoenig.leichtzumerken-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=andrey.grodzovsky-5C7GfCeVMHo@public.gmane.org \
--cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org \
--cc=tomeu-XCtybt49RKsYaV1qd6yewg@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;
as well as URLs for NNTP newsgroup(s).