From: vytskalt via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: vytskalt <VytskaLT@protonmail.com>
Subject: [FFmpeg-devel] hwcontext_vulkan: transfer exclusive images to correct queue family in drm->vulkan mapping
Date: Thu, 31 Jul 2025 23:43:53 +0000
Message-ID: <20250731234342.964712-1-VytskaLT@protonmail.com> (raw)
From: vytskalt <vytskalt@protonmail.com>
VK_QUEUE_FAMILY_IGNORED is only valid when the image is in CONCURRENT
sharing mode. When there is only one queue family it's in the EXCLUSIVE
sharing mode and the dst queue family must match it.
Fixes validation error during drm->vulkan frame mapping:
"pDependencyInfo->pImageMemoryBarriers[0] has srcQueueFamilyIndex
4294967294 (VK_QUEUE_FAMILY_EXTERNAL) and dstQueueFamilyIndex 4294967295
(VK_QUEUE_FAMILY_IGNORED). The command buffer's command pool is
associated with family index 0. Source or destination queue family must
match queue family associated with the command buffer's command pool."
Signed-off-by: vytskalt <vytskalt@protonmail.com>
---
libavutil/hwcontext_vulkan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavutil/hwcontext_vulkan.c b/libavutil/hwcontext_vulkan.c
index 894bc3dae1..6d7df3e619 100644
--- a/libavutil/hwcontext_vulkan.c
+++ b/libavutil/hwcontext_vulkan.c
@@ -3417,7 +3417,7 @@ static int vulkan_map_from_drm_frame_sync(AVHWFramesContext *hwfc, AVFrame *dst,
((flags & AV_HWFRAME_MAP_WRITE) ?
VK_ACCESS_2_SHADER_STORAGE_WRITE_BIT : 0x0),
VK_IMAGE_LAYOUT_GENERAL,
- VK_QUEUE_FAMILY_IGNORED);
+ p->nb_img_qfs > 1 ? VK_QUEUE_FAMILY_IGNORED : p->img_qfs[0]);
vk->CmdPipelineBarrier2(cmd_buf, &(VkDependencyInfo) {
.sType = VK_STRUCTURE_TYPE_DEPENDENCY_INFO,
--
2.49.0
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
reply other threads:[~2025-07-31 23:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250731234342.964712-1-VytskaLT@protonmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=VytskaLT@protonmail.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git