All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Price <steven.price@arm.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Rob Herring <robh+dt@kernel.org>, Icecream95 <ixn@keemail.me>,
	Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
	Robin Murphy <Robin.Murphy@arm.com>
Subject: Re: [PATCH 2/2] drm/panfrost: Propagate panfrost_fence_create() errors to the scheduler
Date: Wed, 5 Feb 2020 14:28:33 +0000	[thread overview]
Message-ID: <20200205142833.GA31873@arm.com> (raw)
In-Reply-To: <20200205152155.2dee52a8@collabora.com>

On Wed, Feb 05, 2020 at 02:21:55PM +0000, Boris Brezillon wrote:
> On Wed, 5 Feb 2020 13:47:55 +0000
> Steven Price <steven.price@arm.com> wrote:
> 
> > On 04/02/2020 14:35, Boris Brezillon wrote:
> > > ->job_run() can return an ERR_PTR() if somethings fails. Let's  
> > > propagate the error returned by panfrost_fence_create() instead of
> > > returning NULL.
> > > 
> > > Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>  
> > 
> > In your previous posting[1] you also handled the case where
> > job->base.s_fence->finished.error is non-zero. Is there a good reason to
> > drop that?
> 
> [2] has been applied in the meantime: returning NULL now preserves
> the finished.error field.

Ah, I'd missed that - looks good.

Thanks,

Steve

> 
> > 
> > [1] https://patchwork.kernel.org/patch/11267153/
> 
> [2]https://patchwork.kernel.org/patch/11218399/
> 
> > 
> > But this change on its own stands, so:
> > 
> > Reviewed-by: Steven Price <steven.price@arm.com>
> > 
> > > ---
> > >  drivers/gpu/drm/panfrost/panfrost_job.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/gpu/drm/panfrost/panfrost_job.c b/drivers/gpu/drm/panfrost/panfrost_job.c
> > > index b0716e49eeca..242147b36d8e 100644
> > > --- a/drivers/gpu/drm/panfrost/panfrost_job.c
> > > +++ b/drivers/gpu/drm/panfrost/panfrost_job.c
> > > @@ -349,7 +349,7 @@ static struct dma_fence *panfrost_job_run(struct drm_sched_job *sched_job)
> > >  
> > >  	fence = panfrost_fence_create(pfdev, slot);
> > >  	if (IS_ERR(fence))
> > > -		return NULL;
> > > +		return fence;
> > >  
> > >  	if (job->done_fence)
> > >  		dma_fence_put(job->done_fence);
> > >   
> > 
> 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-02-05 14:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 14:35 [PATCH 1/2] drm/panfrost: Make sure MMU context lifetime is not bound to panfrost_priv Boris Brezillon
2020-02-04 14:35 ` Boris Brezillon
2020-02-04 14:35 ` [PATCH 2/2] drm/panfrost: Propagate panfrost_fence_create() errors to the scheduler Boris Brezillon
2020-02-04 14:37   ` Alyssa Rosenzweig
2020-02-05 13:47   ` Steven Price
2020-02-05 14:21     ` Boris Brezillon
2020-02-05 14:28       ` Steven Price [this message]
2020-02-04 14:47 ` [PATCH 1/2] drm/panfrost: Make sure MMU context lifetime is not bound to panfrost_priv Boris Brezillon
2020-02-04 14:47   ` Boris Brezillon
2020-02-05 13:39 ` Steven Price
2020-02-05 13:39   ` Steven Price
2020-02-05 14:01   ` Boris Brezillon
2020-02-05 14:01     ` Boris Brezillon
2020-02-05 14:08     ` Steven Price
2020-02-05 14:08       ` Steven Price
2020-02-05 15:45 ` Robin Murphy
2020-02-05 15:45   ` Robin Murphy

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=20200205142833.GA31873@arm.com \
    --to=steven.price@arm.com \
    --cc=Robin.Murphy@arm.com \
    --cc=alyssa.rosenzweig@collabora.com \
    --cc=boris.brezillon@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ixn@keemail.me \
    --cc=robh+dt@kernel.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.