From: "Danilo Krummrich" <dakr@kernel.org>
To: "Lyude Paul" <lyude@redhat.com>
Cc: nouveau@lists.freedesktop.org, 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>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"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>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Asahi Lina" <lina+kernel@asahilina.net>,
"Alyssa Rosenzweig" <alyssa@rosenzweig.io>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Partially revert "rust: drm: gem: Implement AlwaysRefCounted for all gem objects automatically"
Date: Thu, 24 Jul 2025 22:03:24 +0200 [thread overview]
Message-ID: <DBKJYLF9E3TY.IM6UZFA0BW9I@kernel.org> (raw)
In-Reply-To: <20250724191523.561314-1-lyude@redhat.com>
On Thu Jul 24, 2025 at 9:15 PM CEST, Lyude Paul wrote:
> -// SAFETY: All gem objects are refcounted.
> -unsafe impl<T: IntoGEMObject> AlwaysRefCounted for T {
> - 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: NonNull<Self>) {
> - // SAFETY: We either hold the only refcount on `obj`, or one of many - meaning that no one
> - // else could possibly hold a mutable reference to `obj` and thus this immutable reference
> - // is safe.
> - let obj = unsafe { obj.as_ref() }.as_raw();
> -
> - // SAFETY:
> - // - The safety requirements guarantee that the refcount is non-zero.
> - // - We hold no references to `obj` now, making it safe for us to potentially deallocate it.
> - unsafe { bindings::drm_gem_object_put(obj) };
> - }
> -}
IIUC, you'll add rust/kernel/drm/gem/shmem.rs with a new type shmem::Object that
implements IntoGEMObject, right?
If this is correct, I think that should work.
Do I miss anything?
next prev parent reply other threads:[~2025-07-24 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 19:15 [PATCH] Partially revert "rust: drm: gem: Implement AlwaysRefCounted for all gem objects automatically" Lyude Paul
2025-07-24 20:03 ` Danilo Krummrich [this message]
2025-07-24 21:06 ` Lyude Paul
2025-07-24 22:27 ` Danilo Krummrich
2025-07-24 23:13 ` Daniel Almeida
2025-07-25 19:41 ` Lyude Paul
2025-07-28 16:59 ` Danilo Krummrich
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=DBKJYLF9E3TY.IM6UZFA0BW9I@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=alyssa@rosenzweig.io \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--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=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--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;
as well as URLs for NNTP newsgroup(s).