2018-02-13 22:44:08 +00:00
|
|
|
/* GStreamer Intel MSDK plugin
|
|
|
|
* Copyright (c) 2018, Intel Corporation
|
|
|
|
* Copyright (c) 2018, Igalia S.L.
|
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions are met:
|
|
|
|
*
|
|
|
|
* 1. Redistributions of source code must retain the above copyright notice,
|
|
|
|
* this list of conditions and the following disclaimer.
|
|
|
|
*
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright notice,
|
|
|
|
* this list of conditions and the following disclaimer in the documentation
|
|
|
|
* and/or other materials provided with the distribution.
|
|
|
|
*
|
|
|
|
* 3. Neither the name of the copyright holder nor the names of its contributors
|
|
|
|
* may be used to endorse or promote products derived from this software
|
|
|
|
* without specific prior written permission.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
|
|
|
|
* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
|
|
|
|
* THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
|
|
|
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
|
|
|
|
* CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
|
|
|
|
* EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
|
|
|
|
* PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
|
|
|
|
* OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
|
|
|
|
* WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGDECE
|
|
|
|
* OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
|
|
|
|
* EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "gstmsdkbufferpool.h"
|
|
|
|
#include "gstmsdksystemmemory.h"
|
|
|
|
#include "gstmsdkvideomemory.h"
|
2018-03-30 19:06:05 +00:00
|
|
|
#ifndef _WIN32
|
|
|
|
#include "gstmsdkallocator_libva.h"
|
|
|
|
#endif
|
2018-02-13 22:44:08 +00:00
|
|
|
|
|
|
|
GST_DEBUG_CATEGORY_STATIC (gst_debug_msdkbufferpool);
|
|
|
|
#define GST_CAT_DEFAULT gst_debug_msdkbufferpool
|
|
|
|
|
2018-03-30 19:06:05 +00:00
|
|
|
typedef enum _GstMsdkMemoryType
|
|
|
|
{
|
|
|
|
GST_MSDK_MEMORY_TYPE_SYSTEM,
|
|
|
|
GST_MSDK_MEMORY_TYPE_VIDEO,
|
|
|
|
GST_MSDK_MEMORY_TYPE_DMABUF,
|
|
|
|
} GstMsdkMemoryType;
|
|
|
|
|
2018-02-13 22:44:08 +00:00
|
|
|
struct _GstMsdkBufferPoolPrivate
|
|
|
|
{
|
|
|
|
GstMsdkContext *context;
|
|
|
|
GstAllocator *allocator;
|
|
|
|
mfxFrameAllocResponse *alloc_response;
|
2018-03-30 19:06:05 +00:00
|
|
|
GstMsdkMemoryType memory_type;
|
2018-02-13 22:44:08 +00:00
|
|
|
gboolean add_videometa;
|
|
|
|
};
|
|
|
|
|
2018-06-23 22:17:26 +00:00
|
|
|
#define gst_msdk_buffer_pool_parent_class parent_class
|
|
|
|
G_DEFINE_TYPE_WITH_CODE (GstMsdkBufferPool, gst_msdk_buffer_pool,
|
|
|
|
GST_TYPE_VIDEO_BUFFER_POOL, G_ADD_PRIVATE (GstMsdkBufferPool)
|
|
|
|
GST_DEBUG_CATEGORY_INIT (gst_debug_msdkbufferpool, "msdkbufferpool", 0,
|
|
|
|
"MSDK Buffer Pool"));
|
|
|
|
|
2018-02-13 22:44:08 +00:00
|
|
|
static const gchar **
|
|
|
|
gst_msdk_buffer_pool_get_options (GstBufferPool * pool)
|
|
|
|
{
|
|
|
|
static const gchar *options[] = { GST_BUFFER_POOL_OPTION_VIDEO_META,
|
|
|
|
GST_BUFFER_POOL_OPTION_VIDEO_ALIGNMENT,
|
|
|
|
GST_BUFFER_POOL_OPTION_MSDK_USE_VIDEO_MEMORY,
|
2018-03-30 19:06:05 +00:00
|
|
|
GST_BUFFER_POOL_OPTION_MSDK_USE_DMABUF,
|
2018-02-13 22:44:08 +00:00
|
|
|
NULL
|
|
|
|
};
|
|
|
|
|
|
|
|
return options;
|
|
|
|
}
|
|
|
|
|
2019-01-21 17:18:46 +00:00
|
|
|
static inline GstMsdkMemoryType
|
|
|
|
_msdk_get_memory_type (GstStructure * config)
|
|
|
|
{
|
|
|
|
gboolean video, dmabuf;
|
|
|
|
|
|
|
|
video = gst_buffer_pool_config_has_option (config,
|
|
|
|
GST_BUFFER_POOL_OPTION_MSDK_USE_VIDEO_MEMORY);
|
|
|
|
dmabuf = gst_buffer_pool_config_has_option (config,
|
|
|
|
GST_BUFFER_POOL_OPTION_MSDK_USE_DMABUF);
|
|
|
|
|
|
|
|
if (video && !dmabuf)
|
|
|
|
return GST_MSDK_MEMORY_TYPE_VIDEO;
|
|
|
|
if (video && dmabuf)
|
|
|
|
return GST_MSDK_MEMORY_TYPE_DMABUF;
|
|
|
|
if (!video && dmabuf)
|
|
|
|
GST_WARNING ("Can't use DMAbuf since it's system msdk bufferpool");
|
|
|
|
return GST_MSDK_MEMORY_TYPE_SYSTEM;
|
|
|
|
}
|
|
|
|
|
2018-02-13 22:44:08 +00:00
|
|
|
static gboolean
|
|
|
|
gst_msdk_buffer_pool_set_config (GstBufferPool * pool, GstStructure * config)
|
|
|
|
{
|
|
|
|
GstMsdkBufferPool *msdk_pool = GST_MSDK_BUFFER_POOL_CAST (pool);
|
|
|
|
GstMsdkBufferPoolPrivate *priv = msdk_pool->priv;
|
|
|
|
GstCaps *caps = NULL;
|
|
|
|
GstAllocator *allocator = NULL;
|
|
|
|
GstVideoInfo video_info;
|
|
|
|
guint size, min_buffers, max_buffers;
|
|
|
|
|
|
|
|
if (!gst_buffer_pool_config_get_params (config, &caps, &size, &min_buffers,
|
|
|
|
&max_buffers))
|
|
|
|
goto error_invalid_config;
|
|
|
|
|
|
|
|
if (!caps)
|
|
|
|
goto error_no_caps;
|
|
|
|
|
|
|
|
if (!gst_video_info_from_caps (&video_info, caps))
|
|
|
|
goto error_invalid_caps;
|
|
|
|
|
|
|
|
if (!gst_buffer_pool_config_get_allocator (config, &allocator, NULL))
|
|
|
|
goto error_invalid_allocator;
|
|
|
|
|
|
|
|
if (allocator
|
|
|
|
&& (g_strcmp0 (allocator->mem_type, GST_MSDK_SYSTEM_MEMORY_NAME) != 0
|
2018-03-30 19:06:05 +00:00
|
|
|
&& g_strcmp0 (allocator->mem_type, GST_MSDK_VIDEO_MEMORY_NAME) != 0
|
2018-02-13 22:44:08 +00:00
|
|
|
&& g_strcmp0 (allocator->mem_type,
|
2018-03-30 19:06:05 +00:00
|
|
|
GST_MSDK_DMABUF_MEMORY_NAME) != 0)) {
|
2018-02-13 22:44:08 +00:00
|
|
|
GST_INFO_OBJECT (pool,
|
|
|
|
"This is not MSDK allocator. So this will be ignored");
|
|
|
|
gst_object_unref (allocator);
|
|
|
|
allocator = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
priv->add_videometa = gst_buffer_pool_config_has_option (config,
|
|
|
|
GST_BUFFER_POOL_OPTION_VIDEO_META);
|
|
|
|
|
|
|
|
if (priv->add_videometa && gst_buffer_pool_config_has_option (config,
|
|
|
|
GST_BUFFER_POOL_OPTION_VIDEO_ALIGNMENT)) {
|
|
|
|
GstVideoAlignment alignment;
|
|
|
|
|
2019-07-23 05:16:36 +00:00
|
|
|
gst_msdk_set_video_alignment (&video_info, 0, 0, &alignment);
|
2018-02-13 22:44:08 +00:00
|
|
|
gst_video_info_align (&video_info, &alignment);
|
|
|
|
gst_buffer_pool_config_set_video_alignment (config, &alignment);
|
|
|
|
}
|
|
|
|
|
2019-01-21 17:18:46 +00:00
|
|
|
priv->memory_type = _msdk_get_memory_type (config);
|
|
|
|
if (((priv->memory_type == GST_MSDK_MEMORY_TYPE_VIDEO)
|
|
|
|
|| (priv->memory_type == GST_MSDK_MEMORY_TYPE_DMABUF))
|
|
|
|
&& (!priv->context || !priv->alloc_response)) {
|
2018-02-13 22:44:08 +00:00
|
|
|
GST_ERROR_OBJECT (pool,
|
|
|
|
"No MSDK context or Allocation response for using video memory");
|
|
|
|
goto error_invalid_config;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* create a new allocator if needed */
|
|
|
|
if (!allocator) {
|
|
|
|
GstAllocationParams params = { 0, 31, 0, 0, };
|
|
|
|
|
2019-01-21 17:18:46 +00:00
|
|
|
if (priv->memory_type == GST_MSDK_MEMORY_TYPE_DMABUF)
|
2018-03-30 19:06:05 +00:00
|
|
|
allocator =
|
|
|
|
gst_msdk_dmabuf_allocator_new (priv->context, &video_info,
|
|
|
|
priv->alloc_response);
|
2019-01-21 17:18:46 +00:00
|
|
|
else if (priv->memory_type == GST_MSDK_MEMORY_TYPE_VIDEO)
|
2018-02-13 22:44:08 +00:00
|
|
|
allocator =
|
|
|
|
gst_msdk_video_allocator_new (priv->context, &video_info,
|
|
|
|
priv->alloc_response);
|
|
|
|
else
|
|
|
|
allocator = gst_msdk_system_allocator_new (&video_info);
|
|
|
|
|
|
|
|
if (!allocator)
|
|
|
|
goto error_no_allocator;
|
|
|
|
|
|
|
|
GST_INFO_OBJECT (pool, "created new allocator %" GST_PTR_FORMAT, allocator);
|
|
|
|
|
|
|
|
gst_buffer_pool_config_set_allocator (config, allocator, ¶ms);
|
|
|
|
gst_object_unref (allocator);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (priv->allocator)
|
|
|
|
gst_object_unref (priv->allocator);
|
|
|
|
priv->allocator = gst_object_ref (allocator);
|
|
|
|
|
|
|
|
return GST_BUFFER_POOL_CLASS
|
|
|
|
(gst_msdk_buffer_pool_parent_class)->set_config (pool, config);
|
|
|
|
|
|
|
|
error_invalid_config:
|
|
|
|
{
|
|
|
|
GST_ERROR_OBJECT (pool, "invalid config");
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
error_no_caps:
|
|
|
|
{
|
|
|
|
GST_ERROR_OBJECT (pool, "no caps in config");
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
error_invalid_caps:
|
|
|
|
{
|
|
|
|
GST_ERROR_OBJECT (pool, "invalid caps %" GST_PTR_FORMAT, caps);
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
error_invalid_allocator:
|
|
|
|
{
|
|
|
|
GST_ERROR_OBJECT (pool, "no allocator in config");
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
error_no_allocator:
|
|
|
|
{
|
|
|
|
GST_ERROR_OBJECT (pool, "no allocator defined");
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static GstFlowReturn
|
|
|
|
gst_msdk_buffer_pool_alloc_buffer (GstBufferPool * pool,
|
|
|
|
GstBuffer ** out_buffer_ptr, GstBufferPoolAcquireParams * params)
|
|
|
|
{
|
|
|
|
GstMsdkBufferPool *msdk_pool = GST_MSDK_BUFFER_POOL_CAST (pool);
|
|
|
|
GstMsdkBufferPoolPrivate *priv = msdk_pool->priv;
|
|
|
|
GstMemory *mem;
|
|
|
|
GstBuffer *buf;
|
|
|
|
|
|
|
|
buf = gst_buffer_new ();
|
|
|
|
|
2019-01-21 17:18:46 +00:00
|
|
|
if (priv->memory_type == GST_MSDK_MEMORY_TYPE_DMABUF)
|
2018-03-30 19:06:05 +00:00
|
|
|
mem = gst_msdk_dmabuf_memory_new (priv->allocator);
|
2019-01-21 17:18:46 +00:00
|
|
|
else if (priv->memory_type == GST_MSDK_MEMORY_TYPE_VIDEO)
|
2018-02-13 22:44:08 +00:00
|
|
|
mem = gst_msdk_video_memory_new (priv->allocator);
|
|
|
|
else
|
|
|
|
mem = gst_msdk_system_memory_new (priv->allocator);
|
|
|
|
|
|
|
|
if (!mem)
|
|
|
|
goto no_memory;
|
|
|
|
|
|
|
|
gst_buffer_append_memory (buf, mem);
|
|
|
|
|
|
|
|
if (priv->add_videometa) {
|
|
|
|
GstVideoMeta *vmeta;
|
|
|
|
GstVideoInfo *info;
|
|
|
|
|
2019-01-21 17:18:46 +00:00
|
|
|
if (priv->memory_type == GST_MSDK_MEMORY_TYPE_DMABUF)
|
2018-03-30 19:06:05 +00:00
|
|
|
info = &GST_MSDK_DMABUF_ALLOCATOR_CAST (priv->allocator)->image_info;
|
2019-01-21 17:18:46 +00:00
|
|
|
else if (priv->memory_type == GST_MSDK_MEMORY_TYPE_VIDEO)
|
2018-02-13 22:44:08 +00:00
|
|
|
info = &GST_MSDK_VIDEO_ALLOCATOR_CAST (priv->allocator)->image_info;
|
|
|
|
else
|
|
|
|
info = &GST_MSDK_SYSTEM_ALLOCATOR_CAST (priv->allocator)->image_info;
|
|
|
|
|
|
|
|
vmeta = gst_buffer_add_video_meta_full (buf, GST_VIDEO_FRAME_FLAG_NONE,
|
|
|
|
GST_VIDEO_INFO_FORMAT (info),
|
|
|
|
GST_VIDEO_INFO_WIDTH (info), GST_VIDEO_INFO_HEIGHT (info),
|
|
|
|
GST_VIDEO_INFO_N_PLANES (info), info->offset, info->stride);
|
|
|
|
|
2019-01-21 17:18:46 +00:00
|
|
|
if (priv->memory_type == GST_MSDK_MEMORY_TYPE_VIDEO) {
|
2018-02-13 22:44:08 +00:00
|
|
|
vmeta->map = gst_video_meta_map_msdk_memory;
|
|
|
|
vmeta->unmap = gst_video_meta_unmap_msdk_memory;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
*out_buffer_ptr = buf;
|
|
|
|
return GST_FLOW_OK;
|
|
|
|
|
|
|
|
no_memory:
|
|
|
|
{
|
|
|
|
GST_ERROR_OBJECT (pool, "failed to create new MSDK memory");
|
|
|
|
return GST_FLOW_ERROR;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
msdk: manage MSDK surfaces seperately
Currently a gst buffer has one mfxFrameSurface when it's allocated and
can't be changed.
This is based on that the life of gst buffer and mfxFrameSurface would
be same.
But it's not true. Sometimes even if a gst buffer of a frame is finished
on downstream,
mfxFramesurface coupled with the gst buffer is still locked, which means
it's still being used in the driver.
So this patch does this.
Every time a gst buffer is acquired from the pool, it confirms if the
surface coupled with the buffer is unlocked.
If not, replace it with new unlocked one.
In this way, user(decoder or encoder) doesn't need to manage gst buffers
including locked surface.
To do that, this patch includes the following:
1. GstMsdkContext
- Manages MSDK surfaces available, used, locked respectively as the
following:
1\ surfaces_avail : surfaces which are free and unused anywhere
2\ surfaces_used : surfaces coupled with a gst buffer and being used
now.
3\ surfaces_locked : surfaces still locked even after the gst buffer
is released.
- Provide an api to get MSDK surface available.
- Provide an api to release MSDK surface.
2. GstMsdkVideoMemory
- Gets a surface available when it's allocated.
- Provide an api to get an available surface with new unlocked one.
- Provide an api to release surface in the msdk video memory.
3. GstMsdkBufferPool
- In acquire_buffer, every time a gst buffer is acquired, get new
available surface from the list.
- In release_buffer, it confirms if the buffer's surface is unlocked or
not.
- If unlocked, it is put to the available list.
- If still locked, it is put to the locked list.
This also fixes bug #793525.
https://bugzilla.gnome.org/show_bug.cgi?id=793413
https://bugzilla.gnome.org/show_bug.cgi?id=793525
2018-03-08 20:37:12 +00:00
|
|
|
static GstFlowReturn
|
|
|
|
gst_msdk_buffer_pool_acquire_buffer (GstBufferPool * pool,
|
|
|
|
GstBuffer ** out_buffer_ptr, GstBufferPoolAcquireParams * params)
|
|
|
|
{
|
|
|
|
GstMsdkBufferPool *msdk_pool = GST_MSDK_BUFFER_POOL_CAST (pool);
|
|
|
|
GstMsdkBufferPoolPrivate *priv = msdk_pool->priv;
|
|
|
|
GstBuffer *buf = NULL;
|
|
|
|
GstFlowReturn ret;
|
|
|
|
mfxFrameSurface1 *surface;
|
2018-03-30 19:06:05 +00:00
|
|
|
gint fd;
|
msdk: manage MSDK surfaces seperately
Currently a gst buffer has one mfxFrameSurface when it's allocated and
can't be changed.
This is based on that the life of gst buffer and mfxFrameSurface would
be same.
But it's not true. Sometimes even if a gst buffer of a frame is finished
on downstream,
mfxFramesurface coupled with the gst buffer is still locked, which means
it's still being used in the driver.
So this patch does this.
Every time a gst buffer is acquired from the pool, it confirms if the
surface coupled with the buffer is unlocked.
If not, replace it with new unlocked one.
In this way, user(decoder or encoder) doesn't need to manage gst buffers
including locked surface.
To do that, this patch includes the following:
1. GstMsdkContext
- Manages MSDK surfaces available, used, locked respectively as the
following:
1\ surfaces_avail : surfaces which are free and unused anywhere
2\ surfaces_used : surfaces coupled with a gst buffer and being used
now.
3\ surfaces_locked : surfaces still locked even after the gst buffer
is released.
- Provide an api to get MSDK surface available.
- Provide an api to release MSDK surface.
2. GstMsdkVideoMemory
- Gets a surface available when it's allocated.
- Provide an api to get an available surface with new unlocked one.
- Provide an api to release surface in the msdk video memory.
3. GstMsdkBufferPool
- In acquire_buffer, every time a gst buffer is acquired, get new
available surface from the list.
- In release_buffer, it confirms if the buffer's surface is unlocked or
not.
- If unlocked, it is put to the available list.
- If still locked, it is put to the locked list.
This also fixes bug #793525.
https://bugzilla.gnome.org/show_bug.cgi?id=793413
https://bugzilla.gnome.org/show_bug.cgi?id=793525
2018-03-08 20:37:12 +00:00
|
|
|
|
|
|
|
ret =
|
|
|
|
GST_BUFFER_POOL_CLASS (parent_class)->acquire_buffer (pool, &buf, params);
|
|
|
|
|
2018-03-30 19:06:05 +00:00
|
|
|
if (ret != GST_FLOW_OK || priv->memory_type == GST_MSDK_MEMORY_TYPE_SYSTEM) {
|
msdk: manage MSDK surfaces seperately
Currently a gst buffer has one mfxFrameSurface when it's allocated and
can't be changed.
This is based on that the life of gst buffer and mfxFrameSurface would
be same.
But it's not true. Sometimes even if a gst buffer of a frame is finished
on downstream,
mfxFramesurface coupled with the gst buffer is still locked, which means
it's still being used in the driver.
So this patch does this.
Every time a gst buffer is acquired from the pool, it confirms if the
surface coupled with the buffer is unlocked.
If not, replace it with new unlocked one.
In this way, user(decoder or encoder) doesn't need to manage gst buffers
including locked surface.
To do that, this patch includes the following:
1. GstMsdkContext
- Manages MSDK surfaces available, used, locked respectively as the
following:
1\ surfaces_avail : surfaces which are free and unused anywhere
2\ surfaces_used : surfaces coupled with a gst buffer and being used
now.
3\ surfaces_locked : surfaces still locked even after the gst buffer
is released.
- Provide an api to get MSDK surface available.
- Provide an api to release MSDK surface.
2. GstMsdkVideoMemory
- Gets a surface available when it's allocated.
- Provide an api to get an available surface with new unlocked one.
- Provide an api to release surface in the msdk video memory.
3. GstMsdkBufferPool
- In acquire_buffer, every time a gst buffer is acquired, get new
available surface from the list.
- In release_buffer, it confirms if the buffer's surface is unlocked or
not.
- If unlocked, it is put to the available list.
- If still locked, it is put to the locked list.
This also fixes bug #793525.
https://bugzilla.gnome.org/show_bug.cgi?id=793413
https://bugzilla.gnome.org/show_bug.cgi?id=793525
2018-03-08 20:37:12 +00:00
|
|
|
if (buf)
|
|
|
|
*out_buffer_ptr = buf;
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
surface = gst_msdk_get_surface_from_buffer (buf);
|
2019-01-17 08:05:05 +00:00
|
|
|
|
|
|
|
/* When using video memory, mfx surface is still locked even though
|
|
|
|
* it's finished by SyncOperation. There's no way to get notified when it gets unlocked.
|
|
|
|
* So we need to confirm if it's unlocked every time a gst buffer is acquired.
|
|
|
|
* If it's still locked, we can replace it with new unlocked/unused surface.
|
|
|
|
*/
|
msdk: manage MSDK surfaces seperately
Currently a gst buffer has one mfxFrameSurface when it's allocated and
can't be changed.
This is based on that the life of gst buffer and mfxFrameSurface would
be same.
But it's not true. Sometimes even if a gst buffer of a frame is finished
on downstream,
mfxFramesurface coupled with the gst buffer is still locked, which means
it's still being used in the driver.
So this patch does this.
Every time a gst buffer is acquired from the pool, it confirms if the
surface coupled with the buffer is unlocked.
If not, replace it with new unlocked one.
In this way, user(decoder or encoder) doesn't need to manage gst buffers
including locked surface.
To do that, this patch includes the following:
1. GstMsdkContext
- Manages MSDK surfaces available, used, locked respectively as the
following:
1\ surfaces_avail : surfaces which are free and unused anywhere
2\ surfaces_used : surfaces coupled with a gst buffer and being used
now.
3\ surfaces_locked : surfaces still locked even after the gst buffer
is released.
- Provide an api to get MSDK surface available.
- Provide an api to release MSDK surface.
2. GstMsdkVideoMemory
- Gets a surface available when it's allocated.
- Provide an api to get an available surface with new unlocked one.
- Provide an api to release surface in the msdk video memory.
3. GstMsdkBufferPool
- In acquire_buffer, every time a gst buffer is acquired, get new
available surface from the list.
- In release_buffer, it confirms if the buffer's surface is unlocked or
not.
- If unlocked, it is put to the available list.
- If still locked, it is put to the locked list.
This also fixes bug #793525.
https://bugzilla.gnome.org/show_bug.cgi?id=793413
https://bugzilla.gnome.org/show_bug.cgi?id=793525
2018-03-08 20:37:12 +00:00
|
|
|
if (!surface || surface->Data.Locked > 0) {
|
2018-03-30 19:03:00 +00:00
|
|
|
if (!gst_msdk_video_memory_get_surface_available (gst_buffer_peek_memory
|
|
|
|
(buf, 0))) {
|
msdk: manage MSDK surfaces seperately
Currently a gst buffer has one mfxFrameSurface when it's allocated and
can't be changed.
This is based on that the life of gst buffer and mfxFrameSurface would
be same.
But it's not true. Sometimes even if a gst buffer of a frame is finished
on downstream,
mfxFramesurface coupled with the gst buffer is still locked, which means
it's still being used in the driver.
So this patch does this.
Every time a gst buffer is acquired from the pool, it confirms if the
surface coupled with the buffer is unlocked.
If not, replace it with new unlocked one.
In this way, user(decoder or encoder) doesn't need to manage gst buffers
including locked surface.
To do that, this patch includes the following:
1. GstMsdkContext
- Manages MSDK surfaces available, used, locked respectively as the
following:
1\ surfaces_avail : surfaces which are free and unused anywhere
2\ surfaces_used : surfaces coupled with a gst buffer and being used
now.
3\ surfaces_locked : surfaces still locked even after the gst buffer
is released.
- Provide an api to get MSDK surface available.
- Provide an api to release MSDK surface.
2. GstMsdkVideoMemory
- Gets a surface available when it's allocated.
- Provide an api to get an available surface with new unlocked one.
- Provide an api to release surface in the msdk video memory.
3. GstMsdkBufferPool
- In acquire_buffer, every time a gst buffer is acquired, get new
available surface from the list.
- In release_buffer, it confirms if the buffer's surface is unlocked or
not.
- If unlocked, it is put to the available list.
- If still locked, it is put to the locked list.
This also fixes bug #793525.
https://bugzilla.gnome.org/show_bug.cgi?id=793413
https://bugzilla.gnome.org/show_bug.cgi?id=793525
2018-03-08 20:37:12 +00:00
|
|
|
GST_WARNING_OBJECT (pool, "failed to get new surface available");
|
|
|
|
return GST_FLOW_ERROR;
|
|
|
|
}
|
|
|
|
}
|
2018-03-30 19:06:05 +00:00
|
|
|
#ifndef _WIN32
|
|
|
|
/* When using dmabuf, we should confirm that the fd of memeory and
|
|
|
|
* the fd of surface match, since there is no guarantee that fd matches
|
|
|
|
* between surface and memory.
|
|
|
|
*/
|
2019-01-21 17:18:46 +00:00
|
|
|
if (priv->memory_type == GST_MSDK_MEMORY_TYPE_DMABUF) {
|
2018-03-30 19:06:05 +00:00
|
|
|
surface = gst_msdk_get_surface_from_buffer (buf);
|
|
|
|
gst_msdk_get_dmabuf_info_from_surface (surface, &fd, NULL);
|
|
|
|
|
|
|
|
if (gst_dmabuf_memory_get_fd (gst_buffer_peek_memory (buf, 0)) != fd) {
|
|
|
|
GstMemory *mem;
|
|
|
|
mem = gst_msdk_dmabuf_memory_new_with_surface (priv->allocator, surface);
|
|
|
|
gst_buffer_replace_memory (buf, 0, mem);
|
|
|
|
gst_buffer_unset_flags (buf, GST_BUFFER_FLAG_TAG_MEMORY);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
#endif
|
msdk: manage MSDK surfaces seperately
Currently a gst buffer has one mfxFrameSurface when it's allocated and
can't be changed.
This is based on that the life of gst buffer and mfxFrameSurface would
be same.
But it's not true. Sometimes even if a gst buffer of a frame is finished
on downstream,
mfxFramesurface coupled with the gst buffer is still locked, which means
it's still being used in the driver.
So this patch does this.
Every time a gst buffer is acquired from the pool, it confirms if the
surface coupled with the buffer is unlocked.
If not, replace it with new unlocked one.
In this way, user(decoder or encoder) doesn't need to manage gst buffers
including locked surface.
To do that, this patch includes the following:
1. GstMsdkContext
- Manages MSDK surfaces available, used, locked respectively as the
following:
1\ surfaces_avail : surfaces which are free and unused anywhere
2\ surfaces_used : surfaces coupled with a gst buffer and being used
now.
3\ surfaces_locked : surfaces still locked even after the gst buffer
is released.
- Provide an api to get MSDK surface available.
- Provide an api to release MSDK surface.
2. GstMsdkVideoMemory
- Gets a surface available when it's allocated.
- Provide an api to get an available surface with new unlocked one.
- Provide an api to release surface in the msdk video memory.
3. GstMsdkBufferPool
- In acquire_buffer, every time a gst buffer is acquired, get new
available surface from the list.
- In release_buffer, it confirms if the buffer's surface is unlocked or
not.
- If unlocked, it is put to the available list.
- If still locked, it is put to the locked list.
This also fixes bug #793525.
https://bugzilla.gnome.org/show_bug.cgi?id=793413
https://bugzilla.gnome.org/show_bug.cgi?id=793525
2018-03-08 20:37:12 +00:00
|
|
|
|
|
|
|
*out_buffer_ptr = buf;
|
|
|
|
return GST_FLOW_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
gst_msdk_buffer_pool_release_buffer (GstBufferPool * pool, GstBuffer * buf)
|
|
|
|
{
|
|
|
|
mfxFrameSurface1 *surface;
|
|
|
|
GstMsdkBufferPool *msdk_pool = GST_MSDK_BUFFER_POOL_CAST (pool);
|
|
|
|
GstMsdkBufferPoolPrivate *priv = msdk_pool->priv;
|
|
|
|
|
2018-03-30 19:06:05 +00:00
|
|
|
if (priv->memory_type == GST_MSDK_MEMORY_TYPE_SYSTEM)
|
msdk: manage MSDK surfaces seperately
Currently a gst buffer has one mfxFrameSurface when it's allocated and
can't be changed.
This is based on that the life of gst buffer and mfxFrameSurface would
be same.
But it's not true. Sometimes even if a gst buffer of a frame is finished
on downstream,
mfxFramesurface coupled with the gst buffer is still locked, which means
it's still being used in the driver.
So this patch does this.
Every time a gst buffer is acquired from the pool, it confirms if the
surface coupled with the buffer is unlocked.
If not, replace it with new unlocked one.
In this way, user(decoder or encoder) doesn't need to manage gst buffers
including locked surface.
To do that, this patch includes the following:
1. GstMsdkContext
- Manages MSDK surfaces available, used, locked respectively as the
following:
1\ surfaces_avail : surfaces which are free and unused anywhere
2\ surfaces_used : surfaces coupled with a gst buffer and being used
now.
3\ surfaces_locked : surfaces still locked even after the gst buffer
is released.
- Provide an api to get MSDK surface available.
- Provide an api to release MSDK surface.
2. GstMsdkVideoMemory
- Gets a surface available when it's allocated.
- Provide an api to get an available surface with new unlocked one.
- Provide an api to release surface in the msdk video memory.
3. GstMsdkBufferPool
- In acquire_buffer, every time a gst buffer is acquired, get new
available surface from the list.
- In release_buffer, it confirms if the buffer's surface is unlocked or
not.
- If unlocked, it is put to the available list.
- If still locked, it is put to the locked list.
This also fixes bug #793525.
https://bugzilla.gnome.org/show_bug.cgi?id=793413
https://bugzilla.gnome.org/show_bug.cgi?id=793525
2018-03-08 20:37:12 +00:00
|
|
|
goto done;
|
|
|
|
|
|
|
|
surface = gst_msdk_get_surface_from_buffer (buf);
|
|
|
|
if (!surface)
|
|
|
|
goto done;
|
|
|
|
|
2018-03-30 19:03:00 +00:00
|
|
|
gst_msdk_video_memory_release_surface (gst_buffer_peek_memory (buf, 0));
|
msdk: manage MSDK surfaces seperately
Currently a gst buffer has one mfxFrameSurface when it's allocated and
can't be changed.
This is based on that the life of gst buffer and mfxFrameSurface would
be same.
But it's not true. Sometimes even if a gst buffer of a frame is finished
on downstream,
mfxFramesurface coupled with the gst buffer is still locked, which means
it's still being used in the driver.
So this patch does this.
Every time a gst buffer is acquired from the pool, it confirms if the
surface coupled with the buffer is unlocked.
If not, replace it with new unlocked one.
In this way, user(decoder or encoder) doesn't need to manage gst buffers
including locked surface.
To do that, this patch includes the following:
1. GstMsdkContext
- Manages MSDK surfaces available, used, locked respectively as the
following:
1\ surfaces_avail : surfaces which are free and unused anywhere
2\ surfaces_used : surfaces coupled with a gst buffer and being used
now.
3\ surfaces_locked : surfaces still locked even after the gst buffer
is released.
- Provide an api to get MSDK surface available.
- Provide an api to release MSDK surface.
2. GstMsdkVideoMemory
- Gets a surface available when it's allocated.
- Provide an api to get an available surface with new unlocked one.
- Provide an api to release surface in the msdk video memory.
3. GstMsdkBufferPool
- In acquire_buffer, every time a gst buffer is acquired, get new
available surface from the list.
- In release_buffer, it confirms if the buffer's surface is unlocked or
not.
- If unlocked, it is put to the available list.
- If still locked, it is put to the locked list.
This also fixes bug #793525.
https://bugzilla.gnome.org/show_bug.cgi?id=793413
https://bugzilla.gnome.org/show_bug.cgi?id=793525
2018-03-08 20:37:12 +00:00
|
|
|
|
|
|
|
done:
|
2018-12-25 07:10:57 +00:00
|
|
|
GST_BUFFER_POOL_CLASS (parent_class)->release_buffer (pool, buf);
|
msdk: manage MSDK surfaces seperately
Currently a gst buffer has one mfxFrameSurface when it's allocated and
can't be changed.
This is based on that the life of gst buffer and mfxFrameSurface would
be same.
But it's not true. Sometimes even if a gst buffer of a frame is finished
on downstream,
mfxFramesurface coupled with the gst buffer is still locked, which means
it's still being used in the driver.
So this patch does this.
Every time a gst buffer is acquired from the pool, it confirms if the
surface coupled with the buffer is unlocked.
If not, replace it with new unlocked one.
In this way, user(decoder or encoder) doesn't need to manage gst buffers
including locked surface.
To do that, this patch includes the following:
1. GstMsdkContext
- Manages MSDK surfaces available, used, locked respectively as the
following:
1\ surfaces_avail : surfaces which are free and unused anywhere
2\ surfaces_used : surfaces coupled with a gst buffer and being used
now.
3\ surfaces_locked : surfaces still locked even after the gst buffer
is released.
- Provide an api to get MSDK surface available.
- Provide an api to release MSDK surface.
2. GstMsdkVideoMemory
- Gets a surface available when it's allocated.
- Provide an api to get an available surface with new unlocked one.
- Provide an api to release surface in the msdk video memory.
3. GstMsdkBufferPool
- In acquire_buffer, every time a gst buffer is acquired, get new
available surface from the list.
- In release_buffer, it confirms if the buffer's surface is unlocked or
not.
- If unlocked, it is put to the available list.
- If still locked, it is put to the locked list.
This also fixes bug #793525.
https://bugzilla.gnome.org/show_bug.cgi?id=793413
https://bugzilla.gnome.org/show_bug.cgi?id=793525
2018-03-08 20:37:12 +00:00
|
|
|
}
|
|
|
|
|
2018-02-13 22:44:08 +00:00
|
|
|
static void
|
|
|
|
gst_msdk_buffer_pool_finalize (GObject * object)
|
|
|
|
{
|
|
|
|
GstMsdkBufferPool *pool = GST_MSDK_BUFFER_POOL_CAST (object);
|
|
|
|
GstMsdkBufferPoolPrivate *priv = pool->priv;
|
|
|
|
|
|
|
|
if (priv->allocator)
|
|
|
|
gst_object_unref (priv->allocator);
|
|
|
|
|
|
|
|
G_OBJECT_CLASS (parent_class)->finalize (object);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
gst_msdk_buffer_pool_init (GstMsdkBufferPool * pool)
|
|
|
|
{
|
2018-06-23 22:17:26 +00:00
|
|
|
pool->priv = gst_msdk_buffer_pool_get_instance_private (pool);
|
2018-02-13 22:44:08 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
gst_msdk_buffer_pool_class_init (GstMsdkBufferPoolClass * klass)
|
|
|
|
{
|
|
|
|
GObjectClass *object_class = G_OBJECT_CLASS (klass);
|
|
|
|
GstBufferPoolClass *pool_class = GST_BUFFER_POOL_CLASS (klass);
|
|
|
|
|
|
|
|
object_class->finalize = gst_msdk_buffer_pool_finalize;
|
|
|
|
|
|
|
|
pool_class->get_options = gst_msdk_buffer_pool_get_options;
|
|
|
|
pool_class->set_config = gst_msdk_buffer_pool_set_config;
|
|
|
|
pool_class->alloc_buffer = gst_msdk_buffer_pool_alloc_buffer;
|
msdk: manage MSDK surfaces seperately
Currently a gst buffer has one mfxFrameSurface when it's allocated and
can't be changed.
This is based on that the life of gst buffer and mfxFrameSurface would
be same.
But it's not true. Sometimes even if a gst buffer of a frame is finished
on downstream,
mfxFramesurface coupled with the gst buffer is still locked, which means
it's still being used in the driver.
So this patch does this.
Every time a gst buffer is acquired from the pool, it confirms if the
surface coupled with the buffer is unlocked.
If not, replace it with new unlocked one.
In this way, user(decoder or encoder) doesn't need to manage gst buffers
including locked surface.
To do that, this patch includes the following:
1. GstMsdkContext
- Manages MSDK surfaces available, used, locked respectively as the
following:
1\ surfaces_avail : surfaces which are free and unused anywhere
2\ surfaces_used : surfaces coupled with a gst buffer and being used
now.
3\ surfaces_locked : surfaces still locked even after the gst buffer
is released.
- Provide an api to get MSDK surface available.
- Provide an api to release MSDK surface.
2. GstMsdkVideoMemory
- Gets a surface available when it's allocated.
- Provide an api to get an available surface with new unlocked one.
- Provide an api to release surface in the msdk video memory.
3. GstMsdkBufferPool
- In acquire_buffer, every time a gst buffer is acquired, get new
available surface from the list.
- In release_buffer, it confirms if the buffer's surface is unlocked or
not.
- If unlocked, it is put to the available list.
- If still locked, it is put to the locked list.
This also fixes bug #793525.
https://bugzilla.gnome.org/show_bug.cgi?id=793413
https://bugzilla.gnome.org/show_bug.cgi?id=793525
2018-03-08 20:37:12 +00:00
|
|
|
pool_class->acquire_buffer = gst_msdk_buffer_pool_acquire_buffer;
|
|
|
|
pool_class->release_buffer = gst_msdk_buffer_pool_release_buffer;
|
2018-02-13 22:44:08 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
GstBufferPool *
|
|
|
|
gst_msdk_buffer_pool_new (GstMsdkContext * context,
|
|
|
|
mfxFrameAllocResponse * alloc_resp)
|
|
|
|
{
|
|
|
|
GstMsdkBufferPool *pool = g_object_new (GST_TYPE_MSDK_BUFFER_POOL, NULL);
|
|
|
|
|
|
|
|
/* Doesn't need to count reference of the context */
|
|
|
|
pool->priv->context = context;
|
|
|
|
pool->priv->alloc_response = alloc_resp;
|
|
|
|
|
|
|
|
return GST_BUFFER_POOL_CAST (pool);
|
|
|
|
}
|