From: Matej Hrica <mhrica@redhat.com>
To: qemu-devel@nongnu.org
Cc: marcandre.lureau@redhat.com, dbassey@redhat.com,
aesteve@redhat.com, slp@redhat.com,
Matej Hrica <mhrica@redhat.com>
Subject: [RFC PATCH 0/2] vhost-user-gpu: Add support for blob resources
Date: Thu, 18 Jul 2024 14:12:45 +0200 [thread overview]
Message-ID: <20240718121247.181510-1-mhrica@redhat.com> (raw)
Hi,
these patches enable a backend vhost user gpu implementation to support blob
resources.
The first patch simply forwards required feature flags. The second patch
registers a shared memory region for mapping the blob resources in the guest
memory.
I am not sure about the shared memory region creation in the second patch.
Is it fine to rely on the parent object to create the shared memory region?
The parent object should be either virtio-gpu-pci or virtio-vga, though I am
not really sure about the class hierarchy.
These patches are based on this RFC:
[RFC PATCH v2 0/5] vhost-user: Add SHMEM_MAP/UNMAP requests.
Since this relies on an RFC patch, I am also sending this as an RFC too.
Matej Hrica (2):
vhost-user-gpu: Forward RESOURCE_BLOB and CONTEXT_INIT flags
vhost-user-gpu: Add shared memory region support
hw/display/vhost-user-gpu.c | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
--
2.45.2
next reply other threads:[~2024-07-18 12:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 12:12 Matej Hrica [this message]
2024-07-18 12:12 ` [RFC PATCH 1/2] vhost-user-gpu: Forward RESOURCE_BLOB and CONTEXT_INIT flags Matej Hrica
2024-07-18 12:12 ` [RFC PATCH 2/2] vhost-user-gpu: Add shared memory region support Matej Hrica
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=20240718121247.181510-1-mhrica@redhat.com \
--to=mhrica@redhat.com \
--cc=aesteve@redhat.com \
--cc=dbassey@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=slp@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).