From: suijingfeng <suijingfeng@loongson.cn>
To: Maxime Ripard <mripard@kernel.org>,
Javier Martinez Canillas <javierm@redhat.com>
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Emma Anholt <emma@anholt.net>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [05/11] drm/tests: helpers: Create an helper to allocate a locking ctx
Date: Thu, 20 Jul 2023 18:21:17 +0800 [thread overview]
Message-ID: <20cd98b9-23da-62d5-e8b2-4fa18217f326@loongson.cn> (raw)
In-Reply-To: <5khgq6xy4ztci45qtxzo7fyvmdj3i6rrnl5yuny3gusgeeumdq@eobkes722rky>
Hi,
On 2023/7/20 18:07, Maxime Ripard wrote:
> On Wed, Jul 19, 2023 at 09:12:14PM +0200, Javier Martinez Canillas wrote:
>> suijingfeng <suijingfeng@loongson.cn> writes:
>>
>>> Hi,
>>>
>>> On 2023/7/10 15:47, Maxime Ripard wrote:
>> [...]
>>
>>>> +
>>>> +/**
>>>> + * drm_kunit_helper_context_alloc - Allocates an acquire context
>>>> + * @test: The test context object
>>>> + *
>>>> + * Allocates and initializes a modeset acquire context.
>>>> + *
>>>> + * The context is tied to the kunit test context, so we must not call
>>>> + * drm_modeset_acquire_fini() on it, it will be done so automatically.
>>>> + *
>>>> + * Returns:
>>>> + * An ERR_PTR on error, a pointer to the newly allocated context otherwise
>>>> + */
>>>> +struct drm_modeset_acquire_ctx *
>>>> +drm_kunit_helper_acquire_ctx_alloc(struct kunit *test)
>>>> +{
>>>> + struct drm_modeset_acquire_ctx *ctx;
>>>> + int ret;
>>>> +
>>>> + ctx = kunit_kzalloc(test, sizeof(*ctx), GFP_KERNEL);
>>>> + KUNIT_ASSERT_NOT_NULL(test, ctx);
>>>> +
>>>> + drm_modeset_acquire_init(ctx, 0);
>>>> +
>>>> + ret = kunit_add_action_or_reset(test,
>>>> + action_drm_release_context,
>>>> + ctx);
>>>> + if (ret)
>>>> + return ERR_PTR(ret);
>>>> +
>>>> + return ctx;
>>>> +}
>>>> +EXPORT_SYMBOL_GPL(drm_kunit_helper_acquire_ctx_alloc);
>>>> +
>>> I think all of the patch inside this series are quite well.
>>>
>>> Personally, I can't find problems in it.
>>>
>>>
>>> But I still want to ask a question:
>>>
>>> Should the managed functions you introduced be prefixed with drmm_
>>> (instead of drm_) ?
>>>
>> That's a good question. But personally I think that the drmm_ prefix
>> should be reserved for drm_device managed resources and helpers.
> Yeah, to me drmm functions are meant for resources that are tied to the
> DRM device lifetime. These resources are tied to the test lifetime, so
> they shouldn't share the same prefix.
Okay then,
Thanks for reply.
>>> As mindless programmer may still want to call drm_modeset_acquire_fini()
>>> on the pointer returned by
>>>
>>> drm_kunit_helper_acquire_ctx_alloc()?
>>>
>> The function kernel-doc already mentions that there's no need to do that
>> and that will be done automatically by kunit. So shouldn't be different of
>> other functions helper where the programmer didn't read the documentation.
> Right
>
> Maxime
next prev parent reply other threads:[~2023-07-20 10:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 7:47 [PATCH 00/11] drm: kunit: Switch to kunit actions Maxime Ripard
2023-07-10 7:47 ` [PATCH 01/11] drm/tests: helpers: " Maxime Ripard
2023-07-19 18:42 ` Javier Martinez Canillas
2023-07-20 8:51 ` Maxime Ripard
2023-07-10 7:47 ` [PATCH 02/11] drm/tests: client-modeset: Remove call to drm_kunit_helper_free_device() Maxime Ripard
2023-07-19 18:54 ` Javier Martinez Canillas
2023-07-10 7:47 ` [PATCH 03/11] drm/tests: modes: " Maxime Ripard
2023-07-19 18:55 ` Javier Martinez Canillas
2023-07-10 7:47 ` [PATCH 04/11] drm/tests: probe-helper: " Maxime Ripard
2023-07-19 18:56 ` Javier Martinez Canillas
2023-07-10 7:47 ` [PATCH 05/11] drm/tests: helpers: Create an helper to allocate a locking ctx Maxime Ripard
2023-07-17 16:50 ` [05/11] " suijingfeng
2023-07-19 19:12 ` Javier Martinez Canillas
2023-07-20 10:07 ` Maxime Ripard
2023-07-20 10:21 ` suijingfeng [this message]
2023-07-17 17:08 ` suijingfeng
2023-07-19 19:24 ` Javier Martinez Canillas
2023-07-19 19:11 ` [PATCH 05/11] " Javier Martinez Canillas
2023-07-10 7:47 ` [PATCH 06/11] drm/tests: helpers: Create an helper to allocate an atomic state Maxime Ripard
2023-07-19 20:01 ` Javier Martinez Canillas
2023-07-10 7:47 ` [PATCH 07/11] drm/vc4: tests: pv-muxing: Remove call to drm_kunit_helper_free_device() Maxime Ripard
2023-07-19 20:01 ` Javier Martinez Canillas
2023-07-10 7:47 ` [PATCH 08/11] drm/vc4: tests: mock: Use a kunit action to unregister DRM device Maxime Ripard
2023-07-19 20:03 ` Javier Martinez Canillas
2023-07-10 7:47 ` [PATCH 09/11] drm/vc4: tests: pv-muxing: Switch to managed locking init Maxime Ripard
2023-07-17 17:24 ` [09/11] " suijingfeng
2023-07-20 11:06 ` Maxime Ripard
2023-07-19 20:04 ` [PATCH 09/11] " Javier Martinez Canillas
2023-07-10 7:47 ` [PATCH 10/11] drm/vc4: tests: Switch to atomic state allocation helper Maxime Ripard
2023-07-19 20:07 ` Javier Martinez Canillas
2023-07-10 7:47 ` [PATCH 11/11] drm/vc4: tests: pv-muxing: Document test scenario Maxime Ripard
2023-07-19 20:08 ` Javier Martinez Canillas
2023-07-17 15:24 ` [PATCH 00/11] drm: kunit: Switch to kunit actions suijingfeng
2023-07-20 8:19 ` Maxime Ripard
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=20cd98b9-23da-62d5-e8b2-4fa18217f326@loongson.cn \
--to=suijingfeng@loongson.cn \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®