From: Daniel Almeida <daniel.almeida@collabora.com>
To: Deborah Brouwer <deborah.brouwer@collabora.com>
Cc: Alice Ryhl <aliceryhl@google.com>,
Danilo Krummrich <dakr@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Benno Lossin <lossin@kernel.org>, Gary Guo <gary@garyguo.net>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org, boris.brezillon@collabora.com,
samitolvanen@google.com, work@onurozkan.dev, acourbot@nvidia.com,
lyude@redhat.com, laura.nao@collabora.com,
beata.michalska@arm.com, alvin.sun@linux.dev,
steven.price@arm.com
Subject: Re: [PATCH v7 5/7] drm/tyr: add a kernel buffer object
Date: Tue, 21 Jul 2026 14:19:48 -0300 [thread overview]
Message-ID: <2F098DC1-22C5-43DF-A178-F5AA823DCE4C@collabora.com> (raw)
In-Reply-To: <20260713-fw-boot-b4-v7-5-afd8dc1494dd@collabora.com>
> On 14 Jul 2026, at 00:18, Deborah Brouwer <deborah.brouwer@collabora.com> wrote:
>
> Introduce a buffer object type (KernelBo) for internal driver allocations
> that are managed by the kernel rather than userspace.
>
> KernelBo wraps a GEM shmem object and automatically handles GPU virtual
> address space mapping during creation and unmapping on drop. This provides
> a safe and convenient way for the driver to both allocate and clean up
> internal buffers for kernel-managed resources.
>
> Co-developed-by: Boris Brezillon <boris.brezillon@collabora.com>
> Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> Signed-off-by: Deborah Brouwer <deborah.brouwer@collabora.com>
> ---
> drivers/gpu/drm/tyr/gem.rs | 101 +++++++++++++++++++++++++++++++++++++++++++--
> 1 file changed, 97 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/tyr/gem.rs b/drivers/gpu/drm/tyr/gem.rs
> index c28be61a01bb..47a05a33388e 100644
> --- a/drivers/gpu/drm/tyr/gem.rs
> +++ b/drivers/gpu/drm/tyr/gem.rs
> @@ -4,18 +4,29 @@
> //! This module provides buffer object (BO) management functionality using
> //! DRM's GEM subsystem with shmem backing.
>
> +use core::ops::Range;
> +
> use kernel::{
> drm::gem::{
> self,
> shmem, //
> },
> prelude::*,
> - sync::aref::ARef, //
> + sync::{
> + aref::ARef,
> + Arc, //
> + }, //
> };
>
> -use crate::driver::{
> - TyrDrmDevice,
> - TyrDrmDriver, //
> +use crate::{
> + driver::{
> + TyrDrmDevice,
> + TyrDrmDriver, //
> + },
> + vm::{
> + Vm,
> + VmMapFlags, //
> + },
> };
>
> /// Tyr's DriverObject type for GEM objects.
> @@ -56,3 +67,85 @@ pub(crate) fn new_dummy_object(ddev: &TyrDrmDevice) -> Result<ARef<Bo>> {
>
> Ok(bo)
> }
> +
> +/// Specifies how to choose a GPU virtual address for a [`KernelBo`].
> +/// An automatic VA allocation strategy will be added in the future.
> +pub(crate) enum KernelBoVaAlloc {
> + /// Explicit VA address specified by the caller.
> + #[expect(dead_code)]
> + Explicit(u64),
> +}
> +
> +/// A kernel-owned buffer object with automatic GPU virtual address mapping.
> +///
> +/// This structure represents a buffer object that is created and managed entirely
> +/// by the kernel driver, as opposed to userspace-created GEM objects. It combines
> +/// a GEM object with automatic GPU virtual address (VA) space mapping and cleanup.
> +///
> +/// When dropped, the buffer is automatically unmapped from the GPU VA space.
> +pub(crate) struct KernelBo<'bound> {
> + /// The underlying GEM buffer object.
> + #[expect(dead_code)]
> + pub(crate) bo: ARef<Bo>,
Can we make this private?
> + /// The GPU VM this buffer is mapped into.
> + vm: Arc<Vm<'bound>>,
> + /// The GPU VA range occupied by this buffer.
> + va_range: Range<u64>,
> +}
> +
> +impl<'bound> KernelBo<'bound> {
> + /// Creates a new kernel-owned buffer object and maps it into GPU VA space.
> + ///
> + /// This function allocates a new shmem-backed GEM object and immediately maps
> + /// it into the specified GPU virtual memory space. The mapping is automatically
> + /// cleaned up when the [`KernelBo`] is dropped.
> + #[expect(dead_code)]
> + pub(crate) fn new(
> + ddev: &TyrDrmDevice,
> + vm: Arc<Vm<'bound>>,
> + size: u64,
> + va_alloc: KernelBoVaAlloc,
> + flags: VmMapFlags,
> + ) -> Result<Self> {
> + if size == 0 {
> + pr_err!("Cannot create KernelBo with size 0\n");
> + return Err(EINVAL);
> + }
> +
> + let KernelBoVaAlloc::Explicit(va) = va_alloc;
> +
> + let bo = Bo::new(
> + ddev,
> + size as usize,
As a general rule, let’s try our best to reduce the number of `as` casts. Let’s go with
usize::try_from
> + shmem::ObjectConfig {
> + map_wc: true,
> + parent_resv_obj: None,
> + },
> + BoCreateArgs { flags: 0 },
> + )?;
> +
> + vm.map_bo_range(&bo, 0, size, va, flags)?;
> +
> + Ok(KernelBo {
> + bo,
> + vm,
> + va_range: va..(va + size),
> + })
> + }
> +}
> +
> +impl Drop for KernelBo<'_> {
> + fn drop(&mut self) {
> + let va = self.va_range.start;
> + let size = self.va_range.end - self.va_range.start;
> +
> + if let Err(e) = self.vm.unmap_range(va, size) {
> + pr_err!(
> + "Failed to unmap KernelBo range {:#x}..{:#x}: {:?}\n",
> + self.va_range.start,
> + self.va_range.end,
> + e
> + );
> + }
> + }
> +}
>
> --
> 2.54.0
>
next prev parent reply other threads:[~2026-07-21 17:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 3:18 [PATCH v7 0/7] drm/tyr: firmware loading and MCU boot support Deborah Brouwer
2026-07-14 3:18 ` [PATCH v7 1/7] drm/tyr: add resources to RegistrationData Deborah Brouwer
2026-07-14 3:18 ` [PATCH v7 2/7] drm/tyr: add a generic slot manager Deborah Brouwer
2026-07-14 3:18 ` [PATCH v7 3/7] drm/tyr: add Memory Management Unit (MMU) support Deborah Brouwer
2026-07-14 3:18 ` [PATCH v7 4/7] drm/tyr: add GPU virtual memory (VM) support Deborah Brouwer
2026-07-21 12:55 ` Daniel Almeida
2026-07-21 12:58 ` Daniel Almeida
2026-07-21 17:26 ` Danilo Krummrich
2026-07-14 3:18 ` [PATCH v7 5/7] drm/tyr: add a kernel buffer object Deborah Brouwer
2026-07-21 17:19 ` Daniel Almeida [this message]
2026-07-14 3:18 ` [PATCH v7 6/7] drm/tyr: add parser for firmware binary Deborah Brouwer
2026-07-21 20:52 ` Daniel Almeida
2026-07-14 3:18 ` [PATCH v7 7/7] drm/tyr: add Microcontroller Unit (MCU) booting Deborah Brouwer
2026-07-21 21:13 ` Daniel Almeida
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=2F098DC1-22C5-43DF-A178-F5AA823DCE4C@collabora.com \
--to=daniel.almeida@collabora.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=aliceryhl@google.com \
--cc=alvin.sun@linux.dev \
--cc=beata.michalska@arm.com \
--cc=boris.brezillon@collabora.com \
--cc=dakr@kernel.org \
--cc=deborah.brouwer@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=laura.nao@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=simona@ffwll.ch \
--cc=steven.price@arm.com \
--cc=work@onurozkan.dev \
/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