From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH V3 2/2] libavutil/hwcontext_opencl: fix a bug for mapping qsv frame to opencl
Date: Mon, 27 Dec 2021 05:46:01 +0000
Message-ID: <1895d7d08f2b0f80373b9b98f7b0e8c150d3f812.camel@intel.com> (raw)
In-Reply-To: <BY5PR11MB3879D54453BAA4F29A0E2B33F8429@BY5PR11MB3879.namprd11.prod.outlook.com>
On Mon, 2021-12-27 at 03:13 +0000, Chen, Wenbin wrote:
> > On Fri, 2021-12-10 at 13:38 +0800, Wenbin Chen wrote:
> > > From: nyanmisaka <nst799610810@gmail.com>
> > >
> > > mfxHDLPair was added to qsv, so modify qsv->opencl map function as well.
> > > Now the following commandline works:
> > >
> > > ffmpeg -v verbose -init_hw_device vaapi=va:/dev/dri/renderD128 \
> > > -init_hw_device qsv=qs@va -init_hw_device opencl=ocl@va -
> >
> > filter_hw_device ocl
> > > \
> > > -hwaccel qsv -hwaccel_output_format qsv -hwaccel_device qs -c:v
> >
> > h264_qsv \
> > > -i input.264 -vf
> >
> > "hwmap=derive_device=opencl,format=opencl,avgblur_opencl, \
> > > hwmap=derive_device=qsv:reverse=1:extra_hw_frames=32,format=qsv" \
> > > -c:v h264_qsv output.264
> > >
> > > Signed-off-by: nyanmisaka <nst799610810@gmail.com>
> > > Signed-off-by: Wenbin Chen <wenbin.chen@intel.com>
> > > ---
> > > libavutil/hwcontext_opencl.c | 3 ++-
> > > libavutil/hwcontext_qsv.h | 5 +++++
> > > 2 files changed, 7 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/libavutil/hwcontext_opencl.c b/libavutil/hwcontext_opencl.c
> > > index 26a3a24593..ab812999cd 100644
> > > --- a/libavutil/hwcontext_opencl.c
> > > +++ b/libavutil/hwcontext_opencl.c
> > > @@ -48,6 +48,7 @@
> > > #if HAVE_OPENCL_VAAPI_INTEL_MEDIA
> > > #if CONFIG_LIBMFX
> > > #include <mfx/mfxstructures.h>
> > > +#include "hwcontext_qsv.h"
> > > #endif
> > > #include <va/va.h>
> > > #include <CL/cl_va_api_media_sharing_intel.h>
> > > @@ -2249,7 +2250,7 @@ static int
> >
> > opencl_map_from_qsv(AVHWFramesContext
> > > *dst_fc, AVFrame *dst,
> > > #if CONFIG_LIBMFX
> > > if (src->format == AV_PIX_FMT_QSV) {
> > > mfxFrameSurface1 *mfx_surface = (mfxFrameSurface1*)src->data[3];
> > > - va_surface = *(VASurfaceID*)mfx_surface->Data.MemId;
> > > + va_surface = *MFXSURFACEP_TO_VASURFACEP(mfx_surface);
> > > } else
> > > #endif
> > > if (src->format == AV_PIX_FMT_VAAPI) {
> > > diff --git a/libavutil/hwcontext_qsv.h b/libavutil/hwcontext_qsv.h
> > > index b98d611cfc..957df01ef1 100644
> > > --- a/libavutil/hwcontext_qsv.h
> > > +++ b/libavutil/hwcontext_qsv.h
> > > @@ -29,6 +29,11 @@
> > > * contain AVBufferRefs whose data pointer points to an
> >
> > mfxFrameSurface1
> > > struct.
> > > */
> > >
> > > +#if CONFIG_VAAPI
> > > +#define MFXSURFACEP_TO_VASURFACEP(surf) \
> > > + (VASurfaceID*)(((mfxHDLPair*)surf->Data.MemId)->first)
> > > +#endif
> > > +
> >
> > Is it possible to remove the dependency on VAAPI in a public qsv header file
> > ?
> >
> > Thanks
> > Haihao
>
> How about moving this to qsv_internal.h?
>
There is no qsv_internal.h in libavutils. I think we may provide a function
using ff_ as prefix to get the internal vaapi/dxva2/d3d11va handle, user may
call this function and cast the returned handle to the right type in other
hwcontext. If so, we needn't add the dependency on VAAPI in this public header
file.
Thanks
Haihao
_______________________________________________
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:[~2021-12-27 5:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211210053818.3815652-1-wenbin.chen@intel.com>
[not found] ` <20211210053818.3815652-2-wenbin.chen@intel.com>
2021-12-24 6:02 ` Xiang, Haihao
2021-12-27 3:13 ` Chen, Wenbin
2021-12-27 5:46 ` Xiang, Haihao [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=1895d7d08f2b0f80373b9b98f7b0e8c150d3f812.camel@intel.com \
--to=haihao.xiang-at-intel.com@ffmpeg.org \
--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