Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Zhao Zhili <quinkblack@foxmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/2] avutil/hwcontext_vaapi: return ENOSYS for unsupported operation
Date: Sat, 28 Oct 2023 14:36:34 +0800
Message-ID: <tencent_1267CC2A8893279C5F8BBC262BD089A6D806@qq.com> (raw)
In-Reply-To: <8a153ac7-9baa-42e2-97a1-e76002b9ed3f@jkqxz.net>


On 2023/10/28 01:02, Mark Thompson wrote:
> On 27/10/2023 16:37, Zhao Zhili wrote:
>> From: Zhao Zhili <zhilizhao@tencent.com>
>>
>> av_hwframe_transfer_data try with src_ctx first. If the operation
>> failed with AVERROR(ENOSYS), it will try again with dst_ctx. Return
>> AVERROR(EINVAL) makes the second step being skipped.
>> ---
>>   libavutil/hwcontext_vaapi.c | 10 +++++-----
>>   1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/libavutil/hwcontext_vaapi.c b/libavutil/hwcontext_vaapi.c
>> index 558fed94c6..bb28bcf588 100644
>> --- a/libavutil/hwcontext_vaapi.c
>> +++ b/libavutil/hwcontext_vaapi.c
>> @@ -217,7 +217,7 @@ static int 
>> vaapi_get_image_format(AVHWDeviceContext *hwdev,
>>               return 0;
>>           }
>>       }
>> -    return AVERROR(EINVAL);
>> +    return AVERROR(ENOSYS);
>>   }
>>     static int vaapi_frames_get_constraints(AVHWDeviceContext *hwdev,
>> @@ -805,19 +805,19 @@ static int vaapi_map_frame(AVHWFramesContext 
>> *hwfc,
>>         if (!ctx->derive_works && (flags & AV_HWFRAME_MAP_DIRECT)) {
>>           // Requested direct mapping but it is not possible.
>> -        return AVERROR(EINVAL);
>> +        return AVERROR(ENOSYS);
>>       }
>>       if (dst->format == AV_PIX_FMT_NONE)
>>           dst->format = hwfc->sw_format;
>>       if (dst->format != hwfc->sw_format && (flags & 
>> AV_HWFRAME_MAP_DIRECT)) {
>>           // Requested direct mapping but the formats do not match.
>> -        return AVERROR(EINVAL);
>> +        return AVERROR(ENOSYS);
>
> This one seems wrong?  The user requested that (say) a YUV surface is 
> directly mapped to an RGB frame.  That's an invalid request from the 
> user, not an unsupported feature.
>
> If you're changing the return values then this test and the previous 
> one probably want to therefore be in the opposite order as well.

I was thinking about map between hardware pixel format. It's impossible 
for the code path.

Patch v2 removed the change. Thanks for the review.

>
>>       }
>>         err = vaapi_get_image_format(hwfc->device_ctx, dst->format, 
>> &image_format);
>>       if (err < 0) {
>>           // Requested format is not a valid output format.
>> -        return AVERROR(EINVAL);
>> +        return err;
>>       }
>>         map = av_malloc(sizeof(*map));
>> @@ -992,7 +992,7 @@ static int vaapi_map_to_memory(AVHWFramesContext 
>> *hwfc, AVFrame *dst,
>>       if (dst->format != AV_PIX_FMT_NONE) {
>>           err = vaapi_get_image_format(hwfc->device_ctx, dst->format, 
>> NULL);
>>           if (err < 0)
>> -            return AVERROR(ENOSYS);
>> +            return err;
>>       }
>>         err = vaapi_map_frame(hwfc, dst, src, flags);
>
> - Mark
> _______________________________________________
> 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".

_______________________________________________
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:[~2023-10-28  6:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231027153701.246497-1-quinkblack@foxmail.com>
2023-10-27 15:37 ` Zhao Zhili
2023-10-27 16:49   ` Philip Langdale via ffmpeg-devel
2023-10-27 17:02   ` Mark Thompson
2023-10-28  6:36     ` Zhao Zhili [this message]
2023-10-28  6:33   ` [FFmpeg-devel] [PATCH v2 " Zhao Zhili

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=tencent_1267CC2A8893279C5F8BBC262BD089A6D806@qq.com \
    --to=quinkblack@foxmail.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