From: Leo Izen <leo.izen@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 55/97] Vulkan patchset part 2 - hwcontext rewrite and filtering
Date: Fri, 19 May 2023 08:11:00 -0400
Message-ID: <ff8b10ca-e761-ff65-a402-56ae7f7ef3d2@gmail.com> (raw)
In-Reply-To: <NTnyn9K--3-9@lynne.ee>
On 4/24/23 11:56, Lynne wrote:
> This is part two of the vulkan patchset, which contains all the
> hwcontext and vulkan.c rewrites, and filtering changes.
>
> 55 patches attached.
>
>
[PATCH 21/97] lavu: add 12-bit 2-plane 422 and 444 pixel formats
iirc new pixel formats need an APIChanges entry, a lavu micro bump, or
both. I'm not really sure what the policy is but I remember being told
something like that when I added a NE macro a few months ago.
[various]
> static int vulkan_device_create_internal(AVHWDeviceContext *ctx,
> ...
> p->device_features_1_3.foo = dev_features_1_3.foo;
There's a lot of these in various patches, why do these need to be done
manually?
[PATCH 26/97] hwcontext_vulkan: support threadsafe queue and frame
> p->qf_mutex = av_mallocz(qf_num*sizeof(*p->qf_mutex));
av_calloc
+ for (int i = 0; i < qf_num; i++) {
+ p->qf_mutex[i] =
av_mallocz(qf[i].queueCount*sizeof(**p->qf_mutex));
+ if (!p->qf_mutex[i])
+ return AVERROR(ENOMEM);
+ for (int j = 0; j < qf[i].queueCount; j++)
+ pthread_mutex_init(&p->qf_mutex[i][j], NULL);
+ }
If the allocation fails for i > 0, you end up with some initialized
mutexes, is this going to be an issue ever?
@@ -1732,9 +1778,6 @@ static void vulkan_free_internal(AVVkFrame *f)
{
AVVkFrameInternal *internal = f->internal;
- if (!internal)
- return;
-
#if CONFIG_CUDA
if (internal->cuda_fc_ref) {
AVHWFramesContext *cuda_fc = (AVHWFramesContext
*)internal->cuda_fc_ref->data;
What happens if (!internal) and #defined(CONFIG_CUDA), do we just segfault?
- Leo Izen
_______________________________________________
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".
prev parent reply other threads:[~2023-05-19 12:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 15:56 Lynne
2023-04-28 13:28 ` Niklas Haas
[not found] ` <NTnyn9K--3-9@lynne.ee-NTnytIf----9>
2023-05-10 19:10 ` Lynne
2023-05-11 15:36 ` Anton Khirnov
2023-05-11 16:32 ` Lynne
2023-05-11 16:59 ` Anton Khirnov
2023-05-11 16:03 ` Anton Khirnov
2023-05-11 18:55 ` Lynne
2023-05-16 13:31 ` Anton Khirnov
2023-05-16 14:47 ` Lynne
[not found] ` <NV_0sN0--3-9@lynne.ee-NV_0vMs----9>
2023-05-22 8:26 ` Lynne
[not found] ` <NVyq4UQ--F-9@lynne.ee-NW1ZGRp----9>
2023-05-25 0:31 ` Lynne
[not found] ` <NWFJK4e--3-9@lynne.ee-NWFJONn----9>
2023-05-26 17:52 ` Lynne
2023-05-26 19:19 ` Anton Khirnov
2023-05-26 20:50 ` Lynne
2023-05-11 16:05 ` Anton Khirnov
2023-05-11 16:40 ` Lynne
2023-05-11 17:00 ` Anton Khirnov
2023-05-11 16:06 ` Anton Khirnov
2023-05-11 16:45 ` Lynne
2023-05-11 16:14 ` Anton Khirnov
2023-05-11 16:47 ` Lynne
2023-05-11 17:13 ` Anton Khirnov
2023-05-11 16:15 ` Anton Khirnov
2023-05-11 16:50 ` Lynne
2023-05-11 16:21 ` Anton Khirnov
2023-05-11 18:58 ` Lynne
2023-05-16 13:33 ` Anton Khirnov
2023-05-16 14:41 ` Lynne
2023-05-11 16:29 ` Anton Khirnov
2023-05-11 18:13 ` Lynne
2023-05-16 13:40 ` Anton Khirnov
2023-05-16 14:46 ` Lynne
2023-05-18 8:29 ` Anton Khirnov
2023-05-18 12:28 ` Lynne
2023-05-11 16:34 ` Anton Khirnov
2023-05-11 17:12 ` Lynne
2023-05-11 17:19 ` Anton Khirnov
2023-05-11 16:34 ` Anton Khirnov
2023-05-11 17:16 ` Lynne
2023-05-11 16:40 ` Anton Khirnov
2023-05-11 17:20 ` Lynne
2023-05-11 17:27 ` Anton Khirnov
2023-05-11 19:11 ` Lynne
2023-05-18 8:34 ` [FFmpeg-devel] libavcodec: add Vulkan common video code Anton Khirnov
2023-05-18 11:07 ` Lynne
2023-05-18 8:54 ` [FFmpeg-devel] libavcodec: add Vulkan common video decoding code Anton Khirnov
2023-05-18 12:27 ` Lynne
2023-05-19 12:11 ` Leo Izen [this message]
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=ff8b10ca-e761-ff65-a402-56ae7f7ef3d2@gmail.com \
--to=leo.izen@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/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