From: Matthew Auld <matthew.auld@intel.com>
To: "Christian König" <christian.koenig@amd.com>,
intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/4] drm/gem-vram: handle NULL bo->resource in move callback
Date: Tue, 21 Feb 2023 16:26:15 +0000 [thread overview]
Message-ID: <e667ed26-ce67-56e4-c4ae-ea005a081624@intel.com> (raw)
In-Reply-To: <4fb0f24e-d8e7-5482-aa76-07c781d57ffe@amd.com>
On 21/02/2023 16:17, Christian König wrote:
> Am 21.02.23 um 17:13 schrieb Matthew Auld:
>> On 10/02/2023 11:03, Christian König wrote:
>>> Am 08.02.23 um 15:53 schrieb Matthew Auld:
>>>> The ttm BO now initially has NULL bo->resource, and leaves the driver
>>>> the handle that. However it looks like we forgot to handle that for
>>>> ttm_bo_move_memcpy() users, like with vram-gem, since it just silently
>>>> returns zero. This seems to then trigger warnings like:
>>>>
>>>> WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/drm_gem_vram_helper.c:255
>>>> drm_gem_vram_offset (??:?)
>>>>
>>>> Fix this by calling move_null() if the new resource is TTM_PL_SYSTEM,
>>>> otherwise do the multi-hop sequence to ensure can safely call into
>>>> ttm_bo_move_memcpy(), since it might also need to clear the memory.
>>>> This should give the same behaviour as before.
>>>>
>>>> While we are here let's also treat calling ttm_bo_move_memcpy() with
>>>> NULL bo->resource as programmer error, where expectation is that upper
>>>> layers should now handle it.
>>>>
>>>> Fixes: 180253782038 ("drm/ttm: stop allocating dummy resources
>>>> during BO creation")
>>>> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
>>>> Cc: Christian König <christian.koenig@amd.com>
>>>
>>> Oh, I wasn't aware that this broke at so many places. Especially
>>> radeon was tested earlier in the development of the patch set.
>>>
>>> Thanks for looking into that, the radeon patch has my rb and the rest
>>> of the series is Acked-by: Christian König <christian.koenig@amd.com>.
>>
>> Should we go ahead and land this? (minus patch 3 since that is already
>> fixed by vmware folks).
>
> Yeah, sure go ahead.
I assume this has to go via some drm-misc type tree, for which I don't
currently have commit rights. Can you help with merging this?
>
> Thanks,
> Christian.
>
>>
>>>
>>> Regards,
>>> Christian.
>>>
>>>> ---
>>>> drivers/gpu/drm/drm_gem_vram_helper.c | 11 +++++++++++
>>>> drivers/gpu/drm/ttm/ttm_bo_util.c | 4 ++--
>>>> 2 files changed, 13 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/drm_gem_vram_helper.c
>>>> b/drivers/gpu/drm/drm_gem_vram_helper.c
>>>> index d40b3edb52d0..0bea3df2a16d 100644
>>>> --- a/drivers/gpu/drm/drm_gem_vram_helper.c
>>>> +++ b/drivers/gpu/drm/drm_gem_vram_helper.c
>>>> @@ -916,6 +916,17 @@ static int bo_driver_move(struct
>>>> ttm_buffer_object *bo,
>>>> {
>>>> struct drm_gem_vram_object *gbo;
>>>> + if (!bo->resource) {
>>>> + if (new_mem->mem_type != TTM_PL_SYSTEM) {
>>>> + hop->mem_type = TTM_PL_SYSTEM;
>>>> + hop->flags = TTM_PL_FLAG_TEMPORARY;
>>>> + return -EMULTIHOP;
>>>> + }
>>>> +
>>>> + ttm_bo_move_null(bo, new_mem);
>>>> + return 0;
>>>> + }
>>>> +
>>>> gbo = drm_gem_vram_of_bo(bo);
>>>> return drm_gem_vram_bo_driver_move(gbo, evict, ctx, new_mem);
>>>> diff --git a/drivers/gpu/drm/ttm/ttm_bo_util.c
>>>> b/drivers/gpu/drm/ttm/ttm_bo_util.c
>>>> index d9d2b0903b22..fd9fd3d15101 100644
>>>> --- a/drivers/gpu/drm/ttm/ttm_bo_util.c
>>>> +++ b/drivers/gpu/drm/ttm/ttm_bo_util.c
>>>> @@ -157,8 +157,8 @@ int ttm_bo_move_memcpy(struct ttm_buffer_object
>>>> *bo,
>>>> bool clear;
>>>> int ret = 0;
>>>> - if (!src_mem)
>>>> - return 0;
>>>> + if (WARN_ON(!src_mem))
>>>> + return -EINVAL;
>>>> src_man = ttm_manager_type(bdev, src_mem->mem_type);
>>>> if (ttm && ((ttm->page_flags & TTM_TT_FLAG_SWAPPED) ||
>>>
>
next prev parent reply other threads:[~2023-02-21 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 14:53 [Intel-gfx] [PATCH 1/4] drm/gem-vram: handle NULL bo->resource in move callback Matthew Auld
2023-02-08 14:53 ` [Intel-gfx] [PATCH 2/4] drm/qxl: " Matthew Auld
2023-02-08 14:53 ` [Intel-gfx] [PATCH 3/4] drm/vmwgfx: " Matthew Auld
2023-02-08 14:53 ` [Intel-gfx] [PATCH 4/4] drm/radeon: " Matthew Auld
2023-02-08 15:19 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/4] drm/gem-vram: " Patchwork
2023-02-08 19:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-02-09 8:47 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-02-10 11:03 ` [Intel-gfx] [PATCH 1/4] " Christian König
2023-02-21 16:13 ` Matthew Auld
2023-02-21 16:17 ` Christian König
2023-02-21 16:26 ` Matthew Auld [this message]
2023-02-21 16:27 ` Christian König
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=e667ed26-ce67-56e4-c4ae-ea005a081624@intel.com \
--to=matthew.auld@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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