rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alice Ryhl <aliceryhl@google.com>
To: Lyude Paul <lyude@redhat.com>
Cc: dri-devel@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Danilo Krummrich" <dakr@kernel.org>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Asahi Lina" <lina+kernel@asahilina.net>,
	"Shankari Anand" <shankari.ak0208@gmail.com>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/9] rust/drm: Add gem::impl_aref_for_gem_obj!
Date: Fri, 17 Oct 2025 13:22:34 +0000	[thread overview]
Message-ID: <aPJDGqsRFzuARlgP@google.com> (raw)
In-Reply-To: <20251016210955.2813186-3-lyude@redhat.com>

On Thu, Oct 16, 2025 at 05:08:15PM -0400, Lyude Paul wrote:
> In the future we're going to be introducing more GEM object types in rust
> then just gem::Object<T>. Since all types of GEM objects have refcounting,
> let's introduce a macro that we can use in the gem crate in order to copy
> this boilerplate implementation for each type: impl_aref_for_gem_obj!().
> 
> Signed-off-by: Lyude Paul <lyude@redhat.com>
> ---
>  rust/kernel/drm/gem/mod.rs | 53 +++++++++++++++++++++++++++-----------
>  1 file changed, 38 insertions(+), 15 deletions(-)
> 
> diff --git a/rust/kernel/drm/gem/mod.rs b/rust/kernel/drm/gem/mod.rs
> index 20c2769a8c9d6..981fbb931e952 100644
> --- a/rust/kernel/drm/gem/mod.rs
> +++ b/rust/kernel/drm/gem/mod.rs
> @@ -15,6 +15,43 @@
>  };
>  use core::{ops::Deref, ptr::NonNull};
>  
> +/// A macro for implementing [`AlwaysRefCounted`] for any GEM object type.
> +///
> +/// Since all GEM objects use the same refcounting scheme.
> +macro_rules! impl_aref_for_gem_obj {
> +    (
> +        impl $( <$( $tparam_id:ident ),+> )? for $type:ty
> +        $(
> +            where
> +                $( $bind_param:path : $bind_trait:path ),+
> +        )?
> +    ) => {
> +        // SAFETY: All gem objects are refcounted
> +        unsafe impl $( <$( $tparam_id ),+> )? crate::types::AlwaysRefCounted for $type
> +        $(
> +            where
> +                $( $bind_param : $bind_trait ),+
> +        )?
> +        {
> +            fn inc_ref(&self) {
> +                // SAFETY: The existence of a shared reference guarantees that the refcount is
> +                // non-zero.
> +                unsafe { bindings::drm_gem_object_get(self.as_raw()) };
> +            }
> +
> +            unsafe fn dec_ref(obj: core::ptr::NonNull<Self>) {
> +                // SAFETY: `obj` is a valid pointer to an `Object<T>`.
> +                let obj = unsafe { obj.as_ref() };
> +
> +                // SAFETY: The safety requirements guarantee that the refcount is non-zero.
> +                unsafe { bindings::drm_gem_object_put(obj.as_raw()) };

I would prefer to move the call to `.as_raw()` to the `let obj` line so
that the reference more clearly expires before the call to
`drm_gem_object_put()`. The reference must not exist during the call to
`drm_gem_object_put()`.

> +            }
> +        }
> +    };
> +}
> +
> +pub(crate) use impl_aref_for_gem_obj;

The usual way to export macros outside the current file is:

1. Annotated with #[macro_export]
2. Export with `pub use impl_aref_for_gem_obj`

Alice

  reply	other threads:[~2025-10-17 13:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 21:08 [PATCH v4 0/9] Rust bindings for gem shmem + iosys_map Lyude Paul
2025-10-16 21:08 ` [PATCH v4 1/9] Partially revert "rust: drm: gem: Implement AlwaysRefCounted for all gem objects automatically" Lyude Paul
2025-10-17 13:11   ` Alice Ryhl
2025-10-16 21:08 ` [PATCH v4 2/9] rust/drm: Add gem::impl_aref_for_gem_obj! Lyude Paul
2025-10-17 13:22   ` Alice Ryhl [this message]
2025-10-21 17:33     ` Lyude Paul
2025-10-22  8:14       ` Alice Ryhl
2025-10-16 21:08 ` [PATCH v4 3/9] rust: helpers: Add bindings/wrappers for dma_resv_lock Lyude Paul
2025-10-17 13:23   ` Alice Ryhl
2025-10-16 21:08 ` [PATCH v4 4/9] rust: drm: gem: Add raw_dma_resv() function Lyude Paul
2025-10-16 21:08 ` [PATCH v4 5/9] rust: gem: Introduce DriverObject::Args Lyude Paul
2025-10-17 13:24   ` Alice Ryhl
2025-10-16 21:08 ` [PATCH v4 6/9] rust: drm: gem: shmem: Add DRM shmem helper abstraction Lyude Paul
2025-10-17 13:30   ` Alice Ryhl
2025-10-16 21:08 ` [PATCH v4 7/9] rust: drm: gem: Introduce shmem::SGTable Lyude Paul
2025-10-16 21:08 ` [PATCH v4 8/9] rust: Introduce iosys_map bindings Lyude Paul
2025-10-16 22:26   ` Lyude Paul
2025-10-16 21:08 ` [PATCH v4 9/9] rust: drm/gem: Add vmap functions to shmem bindings Lyude Paul

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=aPJDGqsRFzuARlgP@google.com \
    --to=aliceryhl@google.com \
    --cc=a.hindborg@kernel.org \
    --cc=airlied@gmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=lina+kernel@asahilina.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=lyude@redhat.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=shankari.ak0208@gmail.com \
    --cc=simona@ffwll.ch \
    --cc=tmgross@umich.edu \
    /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).