dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/ttm: stop destroying pinned ghost object
Date: Tue, 1 Dec 2020 18:54:40 +0100	[thread overview]
Message-ID: <9d809f2e-7bb6-1b8f-98f5-f33cbe539e5a@gmail.com> (raw)
In-Reply-To: <CAKMK7uGvq4ZDzGuTF_FJ6nVAXS0Stmr4aBdUrbRrES_1ROHs1g@mail.gmail.com>

Am 01.12.20 um 17:58 schrieb Daniel Vetter:
> On Tue, Dec 1, 2020 at 2:32 PM Christian König
> <ckoenig.leichtzumerken@gmail.com> wrote:
>> Daniel added a warning for this, but we were abusing that behavior here.
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> Fixes: 57fcd550eb15 ("drm/ttm: Warn on pinning without holding a reference")
>> ---
>>   drivers/gpu/drm/ttm/ttm_bo_util.c | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/ttm/ttm_bo_util.c b/drivers/gpu/drm/ttm/ttm_bo_util.c
>> index 7ccb2295cac1..5bbc1339d28e 100644
>> --- a/drivers/gpu/drm/ttm/ttm_bo_util.c
>> +++ b/drivers/gpu/drm/ttm/ttm_bo_util.c
>> @@ -310,7 +310,7 @@ static int ttm_buffer_object_transfer(struct ttm_buffer_object *bo,
>>          kref_init(&fbo->base.kref);
>>          fbo->base.destroy = &ttm_transfered_destroy;
>>          fbo->base.acc_size = 0;
>> -       fbo->base.pin_count = 1;
>> +       fbo->base.pin_count = 0;
> Was this just to prevent lru reaping, and let the buffer deletion code
> clean up everything when it's all done? Just kinda freaking out that
> there's no unpin anywhere ...

Yeah, didn't realized how this works before either.

> Anyway tracking ghost objects with the lru like anything else instead
> of tricks with pin count sounds like a good idea.

Well I really want to nuke ghost objects which would be an even better 
idea :)

> Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>

Thanks,
Christian.

>
> But maybe ask Dave or Thomas for a second check.
> -Daniel
>
>>          if (bo->type != ttm_bo_type_sg)
>>                  fbo->base.base.resv = &fbo->base.base._resv;
>>
>> @@ -319,6 +319,8 @@ static int ttm_buffer_object_transfer(struct ttm_buffer_object *bo,
>>          ret = dma_resv_trylock(&fbo->base.base._resv);
>>          WARN_ON(!ret);
>>
>> +       ttm_bo_move_to_lru_tail_unlocked(&fbo->base);
>> +
>>          *new_obj = &fbo->base;
>>          return 0;
>>   }
>> --
>> 2.25.1
>>
>

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2020-12-01 17:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01 13:32 [PATCH] drm/ttm: stop destroying pinned ghost object Christian König
2020-12-01 16:58 ` Daniel Vetter
2020-12-01 17:54   ` 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=9d809f2e-7bb6-1b8f-98f5-f33cbe539e5a@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.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).