From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: "ZhenGuo Yin" <zhenguo.yin@amd.com>,
jingwen.chen2@amd.com,
"Christian König" <christian.koenig@amd.com>,
"ML dri-devel" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/ttm: cleanup the resource of ghost objects after locking them
Date: Thu, 8 Sep 2022 09:51:23 +0200 [thread overview]
Message-ID: <b487ad2f-74f0-4c76-b051-421733ca493e@gmail.com> (raw)
In-Reply-To: <CAM0jSHM-Ozk6zWCirTH_9Ukz2SLiA8qX1pJ0+ZbELOUYdp5UDQ@mail.gmail.com>
Am 08.09.22 um 09:46 schrieb Matthew Auld:
> On Wed, 7 Sept 2022 at 11:26, Matthew Auld
> <matthew.william.auld@gmail.com> wrote:
>> On Wed, 7 Sept 2022 at 11:00, Christian König
>> <ckoenig.leichtzumerken@gmail.com> wrote:
>>> Otherwise lockdep will complain about cleaning up the bulk_move.
>>>
>>> Not even compile tested.
>>>
>>> Signed-off-by: Christian König <christian.koenig@amd.com>
>> Looks reasonable to me,
>> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> Christian, are you going to go ahead and push this one?
Pushed. Thanks for the reminder, just forgot to do that yesterday.
Christian.
>
>>> ---
>>> drivers/gpu/drm/ttm/ttm_bo_util.c | 10 +++++-----
>>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/ttm/ttm_bo_util.c b/drivers/gpu/drm/ttm/ttm_bo_util.c
>>> index 57a27847206f..911141d16e95 100644
>>> --- a/drivers/gpu/drm/ttm/ttm_bo_util.c
>>> +++ b/drivers/gpu/drm/ttm/ttm_bo_util.c
>>> @@ -236,6 +236,11 @@ static int ttm_buffer_object_transfer(struct ttm_buffer_object *bo,
>>> if (bo->type != ttm_bo_type_sg)
>>> fbo->base.base.resv = &fbo->base.base._resv;
>>>
>>> + dma_resv_init(&fbo->base.base._resv);
>>> + fbo->base.base.dev = NULL;
>>> + ret = dma_resv_trylock(&fbo->base.base._resv);
>>> + WARN_ON(!ret);
>>> +
>>> if (fbo->base.resource) {
>>> ttm_resource_set_bo(fbo->base.resource, &fbo->base);
>>> bo->resource = NULL;
>>> @@ -244,11 +249,6 @@ static int ttm_buffer_object_transfer(struct ttm_buffer_object *bo,
>>> fbo->base.bulk_move = NULL;
>>> }
>>>
>>> - dma_resv_init(&fbo->base.base._resv);
>>> - fbo->base.base.dev = NULL;
>>> - ret = dma_resv_trylock(&fbo->base.base._resv);
>>> - WARN_ON(!ret);
>>> -
>>> ret = dma_resv_reserve_fences(&fbo->base.base._resv, 1);
>>> if (ret) {
>>> kfree(fbo);
>>> --
>>> 2.25.1
>>>
prev parent reply other threads:[~2022-09-08 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 10:00 [PATCH] drm/ttm: cleanup the resource of ghost objects after locking them Christian König
2022-09-07 10:10 ` Matthew Auld
2022-09-07 10:26 ` Matthew Auld
2022-09-08 7:46 ` Matthew Auld
2022-09-08 7:51 ` 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=b487ad2f-74f0-4c76-b051-421733ca493e@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingwen.chen2@amd.com \
--cc=matthew.william.auld@gmail.com \
--cc=zhenguo.yin@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox