Rust for Linux List
 help / color / mirror / Atom feed
From: Deborah Brouwer <deborah.brouwer@collabora.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: Lyude Paul <lyude@redhat.com>,
	nouveau@lists.freedesktop.org, Gary Guo <gary@garyguo.net>,
	Daniel Almeida <daniel.almeida@collabora.com>,
	rust-for-linux@vger.kernel.org,
	Danilo Krummrich <dakr@kernel.org>,
	dri-devel@lists.freedesktop.org,
	Matthew Maurer <mmaurer@google.com>,
	FUJITA Tomonori <fujita.tomonori@gmail.com>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	christian.koenig@amd.com, Asahi Lina <lina@asahilina.net>,
	Miguel Ojeda <ojeda@kernel.org>,
	Andreas Hindborg <a.hindborg@kernel.org>,
	Simona Vetter <simona@ffwll.ch>, Boqun Feng <boqun@kernel.org>,
	Sumit Semwal <sumit.semwal@linaro.org>,
	Krishna Ketan Rai <prafulrai522@gmail.com>,
	linux-media@vger.kernel.org,
	Shankari Anand <shankari.ak0208@gmail.com>,
	David Airlie <airlied@gmail.com>,
	Benno Lossin <lossin@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	linaro-mm-sig@lists.linaro.org,
	Asahi Lina <lina+kernel@asahilina.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	kernel@vger.kernel.org
Subject: Re: [PATCH v13 4/5] rust: drm: gem: Introduce shmem::SGTable
Date: Wed, 29 Apr 2026 14:40:25 -0700	[thread overview]
Message-ID: <afJ6ySox_f7g0sfn@um790> (raw)
In-Reply-To: <afG_HUjCMH2qKjPS@google.com>

On Wed, Apr 29, 2026 at 08:19:41AM +0000, Alice Ryhl wrote:
> On Tue, Apr 28, 2026 at 03:03:44PM -0400, Lyude Paul wrote:
> > In order to do this, we need to be careful to ensure that any interface we
> > expose for scatterlists ensures that any mappings created from one are
> > destroyed on driver-unbind. To do this, we introduce a Devres resource into
> > shmem::Object that we use in order to ensure that we release any SGTable
> > mappings on driver-unbind. We store this in an UnsafeCell and protect
> 
> Outdated? No longer UnsafeCell.
> 
> > access to it using the dma_resv lock that we already have from the shmem
> > gem object, which is the same lock that currently protects
> > drm_gem_object_shmem->sgt.
> > 
> > We also provide two different methods for acquiring an sg table:
> > self.sg_table(), and self.owned_sg_table(). The first function is for
> > short-term uses of mapped SGTables, the second is for callers that need to
> > hold onto the mapped SGTable for an extended period of time. The second
> > variant uses Devres of course, whereas the first simply relies on rust's
> > borrow checker to prevent driver-unbind when using the mapped SGTable.
> > 
> > Signed-off-by: Lyude Paul <lyude@redhat.com>
> 
> >      obj: Opaque<bindings::drm_gem_shmem_object>,
> >      /// Parent object that owns this object's DMA reservation object.
> >      parent_resv_obj: Option<ARef<Object<T>>>,
> > +    /// Devres object for unmapping any SGTable on driver-unbind.
> > +    /// TODO: Drop the mutex once we can use Init with SetOnce.
> > +    #[pin]
> > +    sgt_res: Mutex<SetOnce<Devres<SGTableMap<T>>>>,
> 
> As far as I can tell, you don't need this Mutex. Also, it causes
> problems like requiring the reference transmute below.

I think it is also causing a lockdep warning pointing to this sgt_res mutex.
It only happens when KUnit tests are enabled.
If the KUnit tests register a lock class for this mutex first, then when Tyr
later locks it via sg_table(), lockdep complains about the same key being used
for a different class.

> 
> Alice

  reply	other threads:[~2026-04-29 21:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28 19:03 [PATCH v13 0/5] Rust bindings for gem shmem Lyude Paul
2026-04-28 19:03 ` [PATCH v13 1/5] rust: drm: gem: s/device::Device/Device/ for shmem.rs Lyude Paul
2026-04-29  8:05   ` Alice Ryhl
2026-04-28 19:03 ` [PATCH v13 2/5] drm/gem/shmem: Introduce __drm_gem_shmem_free_sgt_locked() Lyude Paul
2026-04-28 19:03 ` [PATCH v13 3/5] rust: drm: gem/shmem: Add DmaResvGuard helper Lyude Paul
2026-04-29  8:11   ` Alice Ryhl
2026-04-29 11:18     ` Alexandre Courbot
2026-04-28 19:03 ` [PATCH v13 4/5] rust: drm: gem: Introduce shmem::SGTable Lyude Paul
2026-04-29  8:19   ` Alice Ryhl
2026-04-29 21:40     ` Deborah Brouwer [this message]
2026-05-01 22:13     ` Lyude Paul
2026-04-28 19:03 ` [PATCH v13 5/5] 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=afJ6ySox_f7g0sfn@um790 \
    --to=deborah.brouwer@collabora.com \
    --cc=a.hindborg@kernel.org \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=boqun@kernel.org \
    --cc=christian.koenig@amd.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fujita.tomonori@gmail.com \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@vger.kernel.org \
    --cc=lina+kernel@asahilina.net \
    --cc=lina@asahilina.net \
    --cc=linaro-mm-sig@lists.linaro.org \
    --cc=linux-media@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=lossin@kernel.org \
    --cc=lyude@redhat.com \
    --cc=mmaurer@google.com \
    --cc=nouveau@lists.freedesktop.org \
    --cc=ojeda@kernel.org \
    --cc=prafulrai522@gmail.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=shankari.ak0208@gmail.com \
    --cc=simona@ffwll.ch \
    --cc=sumit.semwal@linaro.org \
    --cc=viresh.kumar@linaro.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