public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Onur Özkan" <work@onurozkan.dev>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Daniel Almeida" <daniel.almeida@collabora.com>,
	"Boris Brezillon" <boris.brezillon@collabora.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Philipp Stanner" <pstanner@redhat.com>,
	"Sumit Semwal" <sumit.semwal@linaro.org>,
	"Christian König" <christian.koenig@amd.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun@kernel.org>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Trevor Gross" <tmgross@umich.edu>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/gpuvm: rust: add drm_gpuvm_exec support
Date: Wed,  6 May 2026 09:42:33 +0300	[thread overview]
Message-ID: <20260506064240.29720-1-work@onurozkan.dev> (raw)
In-Reply-To: <20260505-gpuvm-drm-exec-v1-2-958306ded36e@google.com>

On Tue, 05 May 2026 13:29:37 +0000
Alice Ryhl <aliceryhl@google.com> wrote:

> This adds support for simple usage of drm_gpuvm_exec() for locking all
> of the dma reservations and adding fences to them. For more complex
> usage that does not involve locking all reservations, it is expected
> that the ww-mutex abstractions will be used instead.
> 
> Signed-off-by: Alice Ryhl <aliceryhl@google.com>
> ---
>  rust/bindings/bindings_helper.h |  2 ++
>  rust/helpers/drm_gpuvm.c        |  6 ++++
>  rust/kernel/dma_buf/mod.rs      | 17 ++++++++++
>  rust/kernel/drm/gpuvm/mod.rs    | 71 +++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 96 insertions(+)
> 
> diff --git a/rust/bindings/bindings_helper.h b/rust/bindings/bindings_helper.h
> index 1124785e210b..3978682a6f2e 100644
> --- a/rust/bindings/bindings_helper.h
> +++ b/rust/bindings/bindings_helper.h
> @@ -151,6 +151,8 @@ const vm_flags_t RUST_CONST_HELPER_VM_MIXEDMAP = VM_MIXEDMAP;
>  const vm_flags_t RUST_CONST_HELPER_VM_HUGEPAGE = VM_HUGEPAGE;
>  const vm_flags_t RUST_CONST_HELPER_VM_NOHUGEPAGE = VM_NOHUGEPAGE;
>  
> +const u32 RUST_CONST_HELPER_DRM_EXEC_INTERRUPTIBLE_WAIT = DRM_EXEC_INTERRUPTIBLE_WAIT;
> +
>  #if IS_ENABLED(CONFIG_GPU_BUDDY)
>  const unsigned long RUST_CONST_HELPER_GPU_BUDDY_RANGE_ALLOCATION = GPU_BUDDY_RANGE_ALLOCATION;
>  const unsigned long RUST_CONST_HELPER_GPU_BUDDY_TOPDOWN_ALLOCATION = GPU_BUDDY_TOPDOWN_ALLOCATION;
> diff --git a/rust/helpers/drm_gpuvm.c b/rust/helpers/drm_gpuvm.c
> index 4130b6325213..30fb1777fbf2 100644
> --- a/rust/helpers/drm_gpuvm.c
> +++ b/rust/helpers/drm_gpuvm.c
> @@ -23,4 +23,10 @@ bool rust_helper_drm_gpuvm_is_extobj(struct drm_gpuvm *gpuvm,
>  	return drm_gpuvm_is_extobj(gpuvm, obj);
>  }
>  
> +__rust_helper
> +void rust_helper_drm_gpuvm_exec_unlock(struct drm_gpuvm_exec *vm_exec)
> +{
> +	drm_gpuvm_exec_unlock(vm_exec);
> +}
> +
>  #endif // CONFIG_RUST_DRM_GPUVM
> diff --git a/rust/kernel/dma_buf/mod.rs b/rust/kernel/dma_buf/mod.rs
> index b66e747c35ad..234936ba8265 100644
> --- a/rust/kernel/dma_buf/mod.rs
> +++ b/rust/kernel/dma_buf/mod.rs
> @@ -5,3 +5,20 @@
>  pub mod dma_fence;
>  
>  pub use self::dma_fence::Fence;
> +
> +/// How the fences from a `dma_resv` obj are used.
> +///
> +/// Please see [the C-side documentation][dma_resv_usage] for more details.
> +///
> +/// [dma_resv_usage]: https://docs.kernel.org/driver-api/dma-buf.html#c.dma_resv_usage
> +#[repr(u32)]
> +pub enum DmaResvUsage {
> +    /// For in kernel memory management only (e.g. copying, clearing memory).
> +    Kernel = bindings::dma_resv_usage_DMA_RESV_USAGE_KERNEL,
> +    /// Implicit write synchronization for userspace submissions.
> +    Write = bindings::dma_resv_usage_DMA_RESV_USAGE_WRITE,
> +    /// Implicit read synchronization for userspace submissions.
> +    Read = bindings::dma_resv_usage_DMA_RESV_USAGE_READ,
> +    /// No implicit sync (e.g. preemption fences, page table updates, TLB flushes).
> +    Bookkeep = bindings::dma_resv_usage_DMA_RESV_USAGE_BOOKKEEP,
> +}
> diff --git a/rust/kernel/drm/gpuvm/mod.rs b/rust/kernel/drm/gpuvm/mod.rs
> index ae58f6f667c1..a52fb25f22ff 100644
> --- a/rust/kernel/drm/gpuvm/mod.rs
> +++ b/rust/kernel/drm/gpuvm/mod.rs
> @@ -16,6 +16,7 @@
>          Flags as AllocFlags, //
>      },
>      bindings,
> +    dma_buf::{DmaResvUsage, Fence},

This can be handled vertically.

>      drm,
>      drm::gem::IntoGEMObject,
>      error::to_result,
> @@ -216,6 +217,30 @@ pub fn obtain(
>          Ok(GpuVmBoAlloc::new(self, obj, data)?.obtain())
>      }
>  
> +    /// Prepare this GPUVM.
> +    ///
> +    /// The parameter indicates how many fences to preallocate space for.
> +    #[inline]
> +    pub fn prepare(&self, num_fences: u32) -> impl PinInit<GpuVmExec<'_, T>, Error> {
> +        try_pin_init!(GpuVmExec {
> +            exec <- Opaque::try_ffi_init(|exec: *mut bindings::drm_gpuvm_exec| {
> +                // SAFETY: exec is valid but unused memory, so we can write.
> +                unsafe {
> +                    ptr::write_bytes(exec, 0u8, 1usize);
> +                    ptr::write(&raw mut (*exec).vm, self.as_raw());
> +                    ptr::write(&raw mut (*exec).flags, bindings::DRM_EXEC_INTERRUPTIBLE_WAIT);
> +                    ptr::write(&raw mut (*exec).num_fences, num_fences);
> +                }
> +
> +                // SAFETY: If successful, this `struct drm_gpuvm_exec` remains valid until this is
> +                // unlocked because it's pinned and unlocks it in drop. The contained pointer to
> +                // `self` remains valid because `GpuVmExec` borrows from `self`.
> +                to_result(unsafe { bindings::drm_gpuvm_exec_lock(exec) })
> +            }),
> +            _gpuvm: PhantomData,
> +        })
> +    }
> +
>      /// Clean up buffer objects that are no longer used.
>      #[inline]
>      pub fn deferred_cleanup(&self) {
> @@ -326,3 +351,49 @@ fn deref(&self) -> &GpuVm<T> {
>          &self.0
>      }
>  }
> +
> +/// The exec token for preparing the objects.
> +///
> +/// # Invariants
> +///
> +/// Owns a GPUVM exec context.
> +#[pin_data(PinnedDrop)]
> +pub struct GpuVmExec<'vm, T: DriverGpuVm> {
> +    #[pin]
> +    exec: Opaque<bindings::drm_gpuvm_exec>,
> +    _gpuvm: PhantomData<&'vm mut GpuVm<T>>,
> +}
> +
> +impl<'vm, T: DriverGpuVm> GpuVmExec<'vm, T> {
> +    /// Add a fence.
> +    ///
> +    /// The caller must ensure that the preallocated space for fences is sufficient.
> +    #[inline]
> +    pub fn resv_add_fence(
> +        &self,
> +        fence: &Fence,
> +        private_usage: DmaResvUsage,
> +        extobj_usage: DmaResvUsage,
> +    ) {
> +        // SAFETY: This method takes a refcount on the fence, so it's only required to be valid for
> +        // the duration of this method. If there is not enough space for the pre-allocated fence,
> +        // then this leads to a BUG_ON() but does not trigger UB.

Did you think about tracking the space of fences? We can store num_fences from
prepare and a counter added_fences then compare them in this function to avoid
this risk.

> +        unsafe {
> +            bindings::drm_gpuvm_resv_add_fence(
> +                (*self.exec.get()).vm,
> +                &raw mut (*self.exec.get()).exec,
> +                fence.as_raw(),
> +                private_usage as u32,
> +                extobj_usage as u32,
> +            )
> +        }
> +    }
> +}
> +
> +#[pinned_drop]
> +impl<'vm, T: DriverGpuVm> PinnedDrop for GpuVmExec<'vm, T> {
> +    fn drop(self: Pin<&mut Self>) {
> +        // SAFETY: We hold the lock, so it's safe to unlock.
> +        unsafe { bindings::drm_gpuvm_exec_unlock(self.exec.get()) };
> +    }
> +}
> 
> -- 
> 2.54.0.545.g6539524ca2-goog
> 

      reply	other threads:[~2026-05-06  6:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 13:29 [PATCH 0/2] Rust support for drm_gpuvm_exec Alice Ryhl
2026-05-05 13:29 ` [PATCH 1/2] rust: dma_buf: add stub dma_fence abstraction Alice Ryhl
2026-05-05 13:29 ` [PATCH 2/2] drm/gpuvm: rust: add drm_gpuvm_exec support Alice Ryhl
2026-05-06  6:42   ` Onur Özkan [this message]

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=20260506064240.29720-1-work@onurozkan.dev \
    --to=work@onurozkan.dev \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=boris.brezillon@collabora.com \
    --cc=christian.koenig@amd.com \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=ojeda@kernel.org \
    --cc=pstanner@redhat.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sumit.semwal@linaro.org \
    --cc=thomas.hellstrom@linux.intel.com \
    --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