All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Dave Emett <david.emett@broadcom.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Thomas Spurden <thomas.spurden@broadcom.com>
Subject: Re: [PATCH 1/4] drm/v3d: Add a note about OOM vs FRDONE, which may be racing on v3.3.
Date: Fri, 22 Mar 2019 14:32:44 -0700	[thread overview]
Message-ID: <87d0mi388z.fsf@anholt.net> (raw)
In-Reply-To: <CAApk1dWqPtCem_BHYVKY47TR8GtvDivY_kg0fv+w+gBZZPnNqA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]

Dave Emett <david.emett@broadcom.com> writes:

> On Wed, 13 Mar 2019 at 23:52, Eric Anholt <eric@anholt.net> wrote:
>>
>> We deref v3d->bin_job in the work handler, but v3d->bin_job doesn't
>> actually hold a ref on the job.
>>
>> Signed-off-by: Eric Anholt <eric@anholt.net>
> Reviewed-by: Dave Emett <david.emett@broadcom.com>
>
>> ---
>>  drivers/gpu/drm/v3d/v3d_irq.c | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/v3d/v3d_irq.c b/drivers/gpu/drm/v3d/v3d_irq.c
>> index b4d6ae81186d..a09442ec7297 100644
>> --- a/drivers/gpu/drm/v3d/v3d_irq.c
>> +++ b/drivers/gpu/drm/v3d/v3d_irq.c
>> @@ -87,7 +87,8 @@ v3d_irq(int irq, void *arg)
>>         if (intsts & V3D_INT_OUTOMEM) {
>>                 /* Note that the OOM status is edge signaled, so the
>>                  * interrupt won't happen again until the we actually
>> -                * add more memory.
>> +                * add more memory.  Also, as of V3D 4.1, FRDONE won't
>> +                * be reported until any OOM state has been cleared.
> Strictly speaking it's FLDONE for bins.

Fixed, thanks.

I'm applying the first 2 of the series for now.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2019-03-22 21:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 23:52 [PATCH 1/4] drm/v3d: Add a note about OOM vs FRDONE, which may be racing on v3.3 Eric Anholt
2019-03-13 23:52 ` [PATCH 2/4] drm/v3d: Rename the fence signaled from IRQs to "irq_fence" Eric Anholt
2019-03-14 11:23   ` Dave Emett
2019-03-13 23:52 ` [PATCH 3/4] drm/v3d: Refactor job management Eric Anholt
2019-03-13 23:52   ` Eric Anholt
2019-03-13 23:52 ` [PATCH 4/4] drm/v3d: Add support for compute shader dispatch Eric Anholt
2019-03-14 11:21 ` [PATCH 1/4] drm/v3d: Add a note about OOM vs FRDONE, which may be racing on v3.3 Dave Emett
2019-03-22 21:32   ` Eric Anholt [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=87d0mi388z.fsf@anholt.net \
    --to=eric@anholt.net \
    --cc=david.emett@broadcom.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.spurden@broadcom.com \
    /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.