aboutsummaryrefslogtreecommitdiffhomepage
path: root/video/out/vulkan/ra_vk.c
diff options
context:
space:
mode:
authorGravatar Philip Langdale <philipl@overt.org>2018-10-14 17:37:05 -0700
committerGravatar sfan5 <sfan5@live.de>2018-10-22 21:35:48 +0200
commita782197d216b2343abe04045b9bb3076864aca80 (patch)
tree6f344aa3c221f073784e695d70d676ae87442cfa /video/out/vulkan/ra_vk.c
parent93f800a00f3f8ef416082e0a3f9d34d979a1e9a6 (diff)
vo_gpu: vulkan: Add arbitrary user data for an ra_vk_buf
This is arguably a little contrived, but in the case of CUDA interop, we have to track additional state on the cuda side for each exported buffer. If we want to be able to manage buffers with an ra_buf_pool, we need some way to keep that CUDA state associated with each created buffer. The easiest way to do that is to attach it directly to the buffers.
Diffstat (limited to 'video/out/vulkan/ra_vk.c')
-rw-r--r--video/out/vulkan/ra_vk.c12
1 files changed, 12 insertions, 0 deletions
diff --git a/video/out/vulkan/ra_vk.c b/video/out/vulkan/ra_vk.c
index 1548b8c785..80019fa4bc 100644
--- a/video/out/vulkan/ra_vk.c
+++ b/video/out/vulkan/ra_vk.c
@@ -693,8 +693,20 @@ struct ra_buf_vk {
// "current" metadata, can change during course of execution
VkPipelineStageFlags current_stage;
VkAccessFlags current_access;
+ // Arbitrary user data for the creator of a buffer
+ void *user_data;
};
+void ra_vk_buf_set_user_data(struct ra_buf *buf, void *user_data) {
+ struct ra_buf_vk *vk_priv = buf->priv;
+ vk_priv->user_data = user_data;
+}
+
+void *ra_vk_buf_get_user_data(struct ra_buf *buf) {
+ struct ra_buf_vk *vk_priv = buf->priv;
+ return vk_priv->user_data;
+}
+
static void vk_buf_deref(struct ra *ra, struct ra_buf *buf)
{
if (!buf)