starred/qemu
1
0
Fork 0
mirror of https://github.com/qemu/qemu.git synced 2026-02-04 05:35:39 +00:00
Code Issues 380 Packages Projects Releases Wiki Activity

[PR #256] [CLOSED] Virtio dmabuf improvements #331

New Issue
Open
opened 2026-01-31 21:30:48 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 21:30:48 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/qemu/qemu/pull/256
Author: @aesteve-rh
Created: 11/7/2023
Status: ❌ Closed

Base: master ← Head: virtio-dmabuf-owner

📝 Commits (3)

  • 82bfebc hw/virtio: check owner for removing objects
  • f4f09d9 hw/virtio: cleanup shared resources
  • 7fe9a4a hw/virtio: rename virtio dmabuf API

📊 Changes

6 files changed (+83 additions, -52 deletions)

View changed files

📝 hw/display/virtio-dmabuf.c (+7 -7)
📝 hw/virtio/vhost-user.c (+26 -7)
📝 hw/virtio/vhost.c (+5 -0)
📝 include/hw/virtio/vhost.h (+6 -0)
📝 include/hw/virtio/virtio-dmabuf.h (+17 -16)
📝 tests/unit/test-virtio-dmabuf.c (+22 -22)

📄 Description

Various improvements for the virtio-dmabuf module.

This patch includes:

  • Check for ownership before allowing a vhost device to remove an object from the table.
  • Properly cleanup shared resources if a vhost device object gets cleaned up.
  • Rename virtio dmabuf functions to virtio_dmabuf_*

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/qemu/qemu/pull/256 **Author:** [@aesteve-rh](https://github.com/aesteve-rh) **Created:** 11/7/2023 **Status:** ❌ Closed **Base:** `master` ← **Head:** `virtio-dmabuf-owner` --- ### 📝 Commits (3) - [`82bfebc`](https://github.com/qemu/qemu/commit/82bfebcbbaeeed36ca62467eb1392ec11879bfd4) hw/virtio: check owner for removing objects - [`f4f09d9`](https://github.com/qemu/qemu/commit/f4f09d90f7112bccb18c2ca98eb1453b89c4160f) hw/virtio: cleanup shared resources - [`7fe9a4a`](https://github.com/qemu/qemu/commit/7fe9a4a1e92c9cf952235fc9545b040518b2f922) hw/virtio: rename virtio dmabuf API ### 📊 Changes **6 files changed** (+83 additions, -52 deletions) <details> <summary>View changed files</summary> 📝 `hw/display/virtio-dmabuf.c` (+7 -7) 📝 `hw/virtio/vhost-user.c` (+26 -7) 📝 `hw/virtio/vhost.c` (+5 -0) 📝 `include/hw/virtio/vhost.h` (+6 -0) 📝 `include/hw/virtio/virtio-dmabuf.h` (+17 -16) 📝 `tests/unit/test-virtio-dmabuf.c` (+22 -22) </details> ### 📄 Description Various improvements for the virtio-dmabuf module. This patch includes: - Check for ownership before allowing a vhost device to remove an object from the table. - Properly cleanup shared resources if a vhost device object gets cleaned up. - Rename virtio dmabuf functions to `virtio_dmabuf_*` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-31 21:30:48 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/qemu#331
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?