All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: Sarah Walker <sarah.walker@imgtec.com>,
	dri-devel@lists.freedesktop.org,
	Luben Tuikov <luben.tuikov@amd.com>,
	Donald Robson <donald.robson@imgtec.com>,
	Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: [PATCH] drm/sched: Call drm_sched_fence_set_parent() from drm_sched_fence_scheduled()
Date: Wed, 21 Jun 2023 16:21:25 +0200	[thread overview]
Message-ID: <20230621162125.1fa29793@collabora.com> (raw)
In-Reply-To: <7333ddbd-6444-a6d5-73b2-4d1648ec4cec@amd.com>

Hi Christian,

On Tue, 13 Jun 2023 13:06:06 +0200
Christian König <christian.koenig@amd.com> wrote:

> Am 13.06.23 um 11:46 schrieb Boris Brezillon:
> > On Tue, 13 Jun 2023 11:44:24 +0200
> > Boris Brezillon <boris.brezillon@collabora.com> wrote:
> >  
> >> Drivers that can delegate waits to the firmware/GPU pass the scheduled
> >> fence to drm_sched_job_add_dependency(), and issue wait commands to
> >> the firmware/GPU at job submission time. For this to be possible, they
> >> need all their 'native' dependencies to have a valid parent since this
> >> is where the actual HW fence information are encoded.
> >>
> >> In drm_sched_main(), we currently call drm_sched_fence_set_parent()
> >> after drm_sched_fence_set_parent(), leaving a short period of time  
> > after drm_sched_fence_scheduled(), ...  
> 
> I was just about to complain, but yeah sounds like the right idea to me.
> 
> Just let me review the patch in more detail.

Did you have time to look at this patch in more detail? Should I send a
v2 fixing the mistake in the commit message?

Regards,

Boris

      reply	other threads:[~2023-06-21 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  9:44 [PATCH] drm/sched: Call drm_sched_fence_set_parent() from drm_sched_fence_scheduled() Boris Brezillon
2023-06-13  9:46 ` Boris Brezillon
2023-06-13 11:06   ` Christian König
2023-06-21 14:21     ` Boris Brezillon [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=20230621162125.1fa29793@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=christian.koenig@amd.com \
    --cc=donald.robson@imgtec.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=luben.tuikov@amd.com \
    --cc=sarah.walker@imgtec.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.