From: "Christian König" <christian.koenig@amd.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: thomas.hellstrom@linux.intel.com, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/ttm: rename ttm_bo_put to _fini
Date: Mon, 7 Jul 2025 14:38:07 +0200 [thread overview]
Message-ID: <4a115c5b-8e91-4ce9-88c7-cf3f3f9d3aa4@amd.com> (raw)
In-Reply-To: <aGWsVBA45EVO/yhM@lstrano-desk.jf.intel.com>
On 03.07.25 00:01, Matthew Brost wrote:
>> diff --git a/drivers/gpu/drm/ttm/tests/ttm_bo_test.c b/drivers/gpu/drm/ttm/tests/ttm_bo_test.c
>> index 6c77550c51af..5426b435f702 100644
>> --- a/drivers/gpu/drm/ttm/tests/ttm_bo_test.c
>> +++ b/drivers/gpu/drm/ttm/tests/ttm_bo_test.c
>> @@ -379,7 +379,7 @@ static void ttm_bo_unreserve_bulk(struct kunit *test)
>> dma_resv_fini(resv);
>> }
>>
>> -static void ttm_bo_put_basic(struct kunit *test)
>> +static void ttm_bo_fini_basic(struct kunit *test)
>> {
>> struct ttm_test_devices *priv = test->priv;
>> struct ttm_buffer_object *bo;
>> @@ -410,7 +410,7 @@ static void ttm_bo_put_basic(struct kunit *test)
>> dma_resv_unlock(bo->base.resv);
>> KUNIT_EXPECT_EQ(test, err, 0);
>>
>> - ttm_bo_put(bo);
>> + ttm_bo_fini(bo);
>
> Intel's CI [1], see Kunit tab, is indicating an issue with the
> selftests.
Even without any change the ttm_bo_validate subtest is crashing for me and I was about to disable those crashing tests.
My guess is that the test never worked 100% reliable and relies on some incorrect assumptions.
> Unsure if this suggestion would fix the kunit failure, but
> would it not be better to just ref count gem BOs in the kunit tests and
> create a mock drm_gem_object_funcs ops in in which free calls
> ttm_bo_fini? Then in selftests replace ttm_bo_fini with
> drm_gem_object_put?
Yeah that is one possible solution I had in mind as well, but I thought about disabling the failed test first and then discussion with Thomas what to do about it.
Christian.
>
> Matt
next prev parent reply other threads:[~2025-07-07 12:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 11:00 Switching TTM over to GEM refcounts v2 Christian König
2025-07-02 11:00 ` [PATCH 1/2] drm/ttm: rename ttm_bo_put to _fini Christian König
2025-07-02 22:01 ` Matthew Brost
2025-07-07 12:38 ` Christian König [this message]
2025-07-07 16:25 ` Matthew Brost
2025-07-07 18:16 ` Christian König
2025-07-02 11:00 ` [PATCH 2/2] drm/ttm: replace TTMs refcount with the DRM refcount v2 Christian König
2025-07-02 12:08 ` ✗ CI.checkpatch: warning for series starting with [1/2] drm/ttm: rename ttm_bo_put to _fini Patchwork
2025-07-02 12:09 ` ✗ CI.KUnit: failure " Patchwork
2025-07-02 16:15 ` Switching TTM over to GEM refcounts v2 Matthew Brost
2025-07-07 10:59 ` 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=4a115c5b-8e91-4ce9-88c7-cf3f3f9d3aa4@amd.com \
--to=christian.koenig@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=thomas.hellstrom@linux.intel.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