From: Wu Jianhua <toqsxw@outlook.com>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Cc: Dmitrii Ovchinnikov <ovchinnikov.dmitrii@gmail.com>
Subject: [FFmpeg-devel] 回复: [PATCH v3] avutil/hwcontext_d3d12va: added resource and heap flags to DeviceContext
Date: Wed, 6 Aug 2025 16:26:33 +0000
Message-ID: <TY7PR01MB146404778BACD0F66BAA2CBF7CA2DA@TY7PR01MB14640.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20250723121006.1047-1-ovchinnikov.dmitrii@gmail.com>
Dmitrii Ovchinnikov:
> ---
> libavutil/hwcontext_d3d12va.c | 17 ++++++++++++++++-
> libavutil/hwcontext_d3d12va.h | 11 +++++++++++
> 2 files changed, 27 insertions(+), 1 deletion(-)
>
> diff --git a/libavutil/hwcontext_d3d12va.c b/libavutil/hwcontext_d3d12va.c
> index 6507cf69c1..dca8ddc0c3 100644
> --- a/libavutil/hwcontext_d3d12va.c
> +++ b/libavutil/hwcontext_d3d12va.c
> @@ -254,7 +254,7 @@ static AVBufferRef *d3d12va_pool_alloc(void *opaque, size_t size)
> if (!frame)
> return NULL;
>
> - if (FAILED(ID3D12Device_CreateCommittedResource(device_hwctx->device, &props, D3D12_HEAP_FLAG_NONE, &desc,
> + if (FAILED(ID3D12Device_CreateCommittedResource(device_hwctx->device, &props, hwctx->heap_flags, &desc,
> D3D12_RESOURCE_STATE_COMMON, NULL, &IID_ID3D12Resource, (void **)&frame->texture))) {
> av_log(ctx, AV_LOG_ERROR, "Could not create the texture\n");
> goto fail;
> @@ -281,6 +281,7 @@ fail:
> static int d3d12va_frames_init(AVHWFramesContext *ctx)
> {
> AVD3D12VAFramesContext *hwctx = ctx->hwctx;
> + AVD3D12VADeviceContext *device_hwctx = ctx->device_ctx->hwctx;
> int i;
>
> for (i = 0; i < FF_ARRAY_ELEMS(supported_formats); i++) {
> @@ -298,6 +299,9 @@ static int d3d12va_frames_init(AVHWFramesContext *ctx)
> return AVERROR(EINVAL);
> }
>
> + hwctx->flags |= device_hwctx->resource_flags;
> + hwctx->heap_flags |= device_hwctx->heap_flags;
> +
> ffhwframesctx(ctx)->pool_internal = av_buffer_pool_init2(sizeof(AVD3D12VAFrame),
> ctx, d3d12va_pool_alloc, NULL);
>
> @@ -673,6 +677,17 @@ static int d3d12va_device_create(AVHWDeviceContext *hwdev, const char *device,
> }
> }
>
> + if (av_dict_get(opts, "UAV", NULL, 0))
> + ctx->resource_flags |= D3D12_RESOURCE_FLAG_ALLOW_UNORDERED_ACCESS;
> +
> + if (av_dict_get(opts, "RTV", NULL, 0))
> + ctx->resource_flags |= D3D12_RESOURCE_FLAG_ALLOW_RENDER_TARGET;
> +
> + ctx->heap_flags = D3D12_HEAP_FLAG_NONE;
> +
> + if (av_dict_get(opts, "SHARED", NULL, 0))
> + ctx->heap_flags |= D3D12_HEAP_FLAG_SHARED;
> +
> return 0;
> }
>
> diff --git a/libavutil/hwcontext_d3d12va.h b/libavutil/hwcontext_d3d12va.h
> index 212a6a6146..0d3a4cc1ec 100644
> --- a/libavutil/hwcontext_d3d12va.h
> +++ b/libavutil/hwcontext_d3d12va.h
> @@ -75,6 +75,16 @@ typedef struct AVD3D12VADeviceContext {
> void (*lock)(void *lock_ctx);
> void (*unlock)(void *lock_ctx);
> void *lock_ctx;
> + /**
> + * Resource flags and Heap flags to be applied to D3D12 resources allocated
> + * for frames using this device context.
> + *
> + * Can be set by the user before initialization via av_hwdevice_ctx_create().
> + *
> + * These apply globally to all frames allocated from this device context.
> + */
> + D3D12_RESOURCE_FLAGS resource_flags;
> + D3D12_HEAP_FLAGS heap_flags;
> } AVD3D12VADeviceContext;
>
> /**
> @@ -137,6 +147,7 @@ typedef struct AVD3D12VAFramesContext {
> * @see https://learn.microsoft.com/en-us/windows/win32/api/d3d12/ne-d3d12-d3d12_resource_flags
> */
> D3D12_RESOURCE_FLAGS flags;
> + D3D12_HEAP_FLAGS heap_flags;
> } AVD3D12VAFramesContext;
>
> #endif /* AVUTIL_HWCONTEXT_D3D12VA_H */
> --
> 2.47.1.windows.1
Hi there,
This patch looks good to me. Will push if there is no more comments.
Thanks,
Jianhua
_______________________________________________
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:[~2025-08-06 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 12:10 [FFmpeg-devel] " Dmitrii Ovchinnikov
2025-08-06 16:26 ` Wu Jianhua [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=TY7PR01MB146404778BACD0F66BAA2CBF7CA2DA@TY7PR01MB14640.jpnprd01.prod.outlook.com \
--to=toqsxw@outlook.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=ovchinnikov.dmitrii@gmail.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