<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/building-tyr-in-rust-part-3-managing-gpu-memory-pi8jvzwe4" -->

---
title: Building Tyr in Rust, part 3: Managing GPU memory
description: This deep technical dive continues Collabora's series on Tyr, a Rust GPU kernel driver for Mali hardware, focusing on GPU memory management. It covers VM_BIND...
canonical: https://daily.dev/posts/building-tyr-in-rust-part-3-managing-gpu-memory-pi8jvzwe4
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Building Tyr in Rust, part 3: Managing GPU memory | daily.dev
og:description: This deep technical dive continues Collabora's series on Tyr, a Rust GPU kernel driver for Mali hardware, focusing on GPU memory management. It covers VM_BIND...
og:url: https://daily.dev/posts/building-tyr-in-rust-part-3-managing-gpu-memory-pi8jvzwe4
og:image: https://api.daily.dev/og/posts/PI8JVZWe4.png
og:image:alt: Building Tyr in Rust, part 3: Managing GPU memory
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Building Tyr in Rust, part 3: Managing GPU memory

**[Collabora Blog](https://daily.dev/sources/collabora)** · 17 min read · 4 upvotes · 0 comments

## Summary

This deep technical dive continues Collabora's series on Tyr, a Rust GPU kernel driver for Mali hardware, focusing on GPU memory management. It covers VM_BIND operations for mapping physical memory to GPU virtual addresses, the role of the IOMMU and ARM64 LPAE page tables, Mali's limited address space slots, the GPUVM kernel framework for shared VA management logic, and the GEM memory manager using shmfs-backed buffers for allocation. The piece ties these mechanisms together by retelling how the MCU firmware boots using VM_BIND, and notes that Tyr's VM layer, GPUVM Rust bindings, and GEM abstractions have now landed upstream in drm-rust-next, while userspace-facing ioctls remain downstream. The next installment will cover synchronization via DMA fences and job scheduling.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.collabora.com/news-and-blog/blog/2026/08/26/building-tyr-in-rust-part-3-managing-gpu-memory>

## Questions this post answers

### What is the VM_BIND operation in a Linux GPU kernel driver used for?

VM_BIND maps a section of a buffer object to a range of GPU virtual addresses, and the collection of such mappings forms a VM. It can run synchronously, blocking until complete, or asynchronously as a job submission with its own signaling. In Panthor and Tyr it is exposed through the drm_panthor_vm_bind ioctl and is essential for booting firmware and backing Vulkan device memory.

_Developers building or debugging GPU drivers can follow deep dives like this on daily.dev to track VM_BIND and GPUVM internals._

### How does the GEM memory manager allocate GPU buffers on GPUs without dedicated VRAM, like Mali?

GEM uses shmfs to allocate anonymous, pageable memory as backing storage for buffer objects, since Panthor and Tyr rely on system memory rather than VRAM. These shmem-backed pages come from the kernel's page allocator like any other anonymous memory, making GPU buffers swappable, though pages are pinned while a context is actively executing on the GPU.

_Anyone comparing GEM versus TTM for GPU memory backing can keep up with driver internals like these on daily.dev._

### What is GPUVM and why does a Rust GPU kernel driver need a Rust interface to it?

GPUVM is a shared Linux kernel component that manages a GPU's virtual address space, computing the map, unmap, and remap operations needed when a driver requests changes, including correctly decomposing partial unmaps into multiple resulting mappings. Tyr's VM layer is built on a Rust GPUVM abstraction that did not exist before this driver needed it, with map, unmap, and remap hooks implemented as safe Rust code.

_Kernel developers writing Rust GPU drivers can track upstreaming progress on abstractions like GPUVM through daily.dev._

## Similar posts on daily.dev

- [The future for Tyr](https://daily.dev/posts/the-future-for-tyr-xdzk3dk6f) · Hacker News · 1 upvotes · 0 comments
- [Building GPU Drivers in Rust: Tyr at RustConf 2026](https://daily.dev/posts/building-gpu-drivers-in-rust-tyr-at-rustconf-2026-db6pg3qtl) · Collabora Blog · 13 upvotes · 2 comments
- [Upstreaming Tyr: Rust, DRM, and the Linux Kernel \(Collabora\)](https://daily.dev/posts/upstreaming-tyr-rust-drm-and-the-linux-kernel-collabora--oowhua7z6) · LWN.net · 2 upvotes · 0 comments
- [Rust-Based Arm GPU Kernel Driver "Tyr" Begins Running GNOME & Basic Games](https://daily.dev/posts/rust-based-arm-gpu-kernel-driver-tyr-begins-running-gnome-basic-games-8w2bxxznp) · Phoronix · 0 upvotes · 0 comments
- [Kernel 7.2: RK3588 media, smarter GPU memory, and Rust foundations](https://daily.dev/posts/kernel-7-2-rk3588-media-smarter-gpu-memory-and-rust-foundations-vrpih8voj) · Collabora Blog · 0 upvotes · 0 comments

---

Tags: [#linux](https://daily.dev/tags/linux), [#rust](https://daily.dev/tags/rust)

[View this post on daily.dev](https://daily.dev/posts/building-tyr-in-rust-part-3-managing-gpu-memory-pi8jvzwe4)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Building Tyr in Rust, part 3: Managing GPU memory","url":"https://daily.dev/posts/building-tyr-in-rust-part-3-managing-gpu-memory-pi8jvzwe4","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/building-tyr-in-rust-part-3-managing-gpu-memory-pi8jvzwe4"},"datePublished":"2026-08-26T18:10:37.660Z","dateModified":"2026-09-14T07:19:30.727Z","description":"This deep technical dive continues Collabora's series on Tyr, a Rust GPU kernel driver for Mali hardware, focusing on GPU memory management. It covers VM_BIND...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/46890877f4693da6cb4b423c4e540f2c?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/46890877f4693da6cb4b423c4e540f2c?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Collabora Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collabora Blog","logo":"https://media.daily.dev/image/upload/s--ZGZ0FjqS--/f_auto,q_auto/v1786438306/logos/collabora?_a=BAMAMicg0","url":"https://daily.dev/sources/collabora"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/building-tyr-in-rust-part-3-managing-gpu-memory-pi8jvzwe4","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":4},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"linux,rust","timeRequired":"PT17M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collabora Blog","item":"https://daily.dev/sources/collabora"},{"@type":"ListItem","position":3,"name":"Building Tyr in Rust, part 3: Managing GPU memory"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/building-tyr-in-rust-part-3-managing-gpu-memory-pi8jvzwe4#faq","mainEntity":[{"@type":"Question","name":"What is the VM_BIND operation in a Linux GPU kernel driver used for?","acceptedAnswer":{"@type":"Answer","text":"VM_BIND maps a section of a buffer object to a range of GPU virtual addresses, and the collection of such mappings forms a VM. It can run synchronously, blocking until complete, or asynchronously as a job submission with its own signaling. In Panthor and Tyr it is exposed through the drm_panthor_vm_bind ioctl and is essential for booting firmware and backing Vulkan device memory. Developers building or debugging GPU drivers can follow deep dives like this on daily.dev to track VM_BIND and GPUVM internals."}},{"@type":"Question","name":"How does the GEM memory manager allocate GPU buffers on GPUs without dedicated VRAM, like Mali?","acceptedAnswer":{"@type":"Answer","text":"GEM uses shmfs to allocate anonymous, pageable memory as backing storage for buffer objects, since Panthor and Tyr rely on system memory rather than VRAM. These shmem-backed pages come from the kernel's page allocator like any other anonymous memory, making GPU buffers swappable, though pages are pinned while a context is actively executing on the GPU. Anyone comparing GEM versus TTM for GPU memory backing can keep up with driver internals like these on daily.dev."}},{"@type":"Question","name":"What is GPUVM and why does a Rust GPU kernel driver need a Rust interface to it?","acceptedAnswer":{"@type":"Answer","text":"GPUVM is a shared Linux kernel component that manages a GPU's virtual address space, computing the map, unmap, and remap operations needed when a driver requests changes, including correctly decomposing partial unmaps into multiple resulting mappings. Tyr's VM layer is built on a Rust GPUVM abstraction that did not exist before this driver needed it, with map, unmap, and remap hooks implemented as safe Rust code. Kernel developers writing Rust GPU drivers can track upstreaming progress on abstractions like GPUVM through daily.dev."}}]}
```

