From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Cc: "Chow, Hon Wai" <hon.wai.chow@intel.com>, "Rogozhkin, Dmitry V" <dmitry.v.rogozhkin@intel.com> Subject: Re: [FFmpeg-devel] [PATCH] qsv: Update ffmpeg qsv_errors to recognize GPU hang and other statuses Date: Thu, 28 Jul 2022 06:24:10 +0000 Message-ID: <6b4babc2c20c8c9aa096495cd2c85d253c145561.camel@intel.com> (raw) In-Reply-To: <1658762854-28777-1-git-send-email-dmitry.v.rogozhkin@intel.com> On Mon, 2022-07-25 at 08:27 -0700, Dmitry Rogozhkin wrote: > GPU hang is one of the most typical errors on Intel GPUs in > case something goes wrong. It's important to recognize it > explicitly for easier bugs triage. Also, this error code > can be used to trigger GPU recovery path in self-written > applications. > > There were 2 other statuses which MediaSDK can ppotentially return, > MFX_ERR_NONE_PARTIAL_OUTPUT and MFX_ERR_REALLOC_SURFACE. Adding > them as well. > > Signed-off-by: Hon Wai Chow <hon.wai.chow@intel.com> > Signed-off-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com> > --- > libavcodec/qsv.c | 5 +++++ > libavfilter/qsvvpp.c | 5 +++++ > 2 files changed, 10 insertions(+) > > diff --git a/libavcodec/qsv.c b/libavcodec/qsv.c > index 385b43b..70918b1 100644 > --- a/libavcodec/qsv.c > +++ b/libavcodec/qsv.c > @@ -105,6 +105,9 @@ static const struct { > const char *desc; > } qsv_errors[] = { > { > MFX_ERR_NONE, 0, "success" > }, > +#if QSV_VERSION_ATLEAST(1, 31) > + { MFX_ERR_NONE_PARTIAL_OUTPUT, 0, "partial MFX_ERR_NONE_PARTIAL_OUTPUT is 12 which is actually a warning defined in theSDK, could you move this to the end of warnings in this arrary ? > output" }, > +#endif > { MFX_ERR_UNKNOWN, AVERROR_UNKNOWN, "unknown > error" }, > { MFX_ERR_NULL_PTR, AVERROR(EINVAL), "NULL > pointer" }, > { MFX_ERR_UNSUPPORTED, AVERROR(ENOSYS), > "unsupported" }, > @@ -125,6 +128,8 @@ static const struct { > { MFX_ERR_INVALID_VIDEO_PARAM, AVERROR(EINVAL), "invalid video > parameters" }, > { MFX_ERR_UNDEFINED_BEHAVIOR, AVERROR_BUG, "undefined > behavior" }, > { MFX_ERR_DEVICE_FAILED, AVERROR(EIO), "device > failed" }, > + { MFX_ERR_GPU_HANG, AVERROR(EIO), "GPU > Hang" }, > + { MFX_ERR_REALLOC_SURFACE, AVERROR_UNKNOWN, "need bigger surface > for output" }, > { MFX_ERR_INCOMPATIBLE_AUDIO_PARAM, AVERROR(EINVAL), "incompatible audio > parameters" }, > { MFX_ERR_INVALID_AUDIO_PARAM, AVERROR(EINVAL), "invalid audio > parameters" }, > > diff --git a/libavfilter/qsvvpp.c b/libavfilter/qsvvpp.c > index 954f882..2f0613f 100644 > --- a/libavfilter/qsvvpp.c > +++ b/libavfilter/qsvvpp.c > @@ -80,6 +80,9 @@ static const struct { > const char *desc; > } qsv_errors[] = { > { > MFX_ERR_NONE, 0, "success" > }, > +#if QSV_VERSION_ATLEAST(1, 31) > + { MFX_ERR_NONE_PARTIAL_OUTPUT, 0, "partial Same as above. Thanks Haihao > output" }, > +#endif > { MFX_ERR_UNKNOWN, AVERROR_UNKNOWN, "unknown > error" }, > { MFX_ERR_NULL_PTR, AVERROR(EINVAL), "NULL > pointer" }, > { MFX_ERR_UNSUPPORTED, AVERROR(ENOSYS), > "unsupported" }, > @@ -100,6 +103,8 @@ static const struct { > { MFX_ERR_INVALID_VIDEO_PARAM, AVERROR(EINVAL), "invalid video > parameters" }, > { MFX_ERR_UNDEFINED_BEHAVIOR, AVERROR_BUG, "undefined > behavior" }, > { MFX_ERR_DEVICE_FAILED, AVERROR(EIO), "device > failed" }, > + { MFX_ERR_GPU_HANG, AVERROR(EIO), "GPU > Hang" }, > + { MFX_ERR_REALLOC_SURFACE, AVERROR_UNKNOWN, "need bigger surface > for output" }, > { MFX_ERR_INCOMPATIBLE_AUDIO_PARAM, AVERROR(EINVAL), "incompatible audio > parameters" }, > { MFX_ERR_INVALID_AUDIO_PARAM, AVERROR(EINVAL), "invalid audio > parameters" }, > _______________________________________________ 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".
next prev parent reply other threads:[~2022-07-28 6:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-25 15:27 Dmitry Rogozhkin 2022-07-28 6:24 ` Xiang, Haihao [this message] 2022-07-28 15:19 Dmitry Rogozhkin 2022-07-29 5:03 ` Xiang, Haihao
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=6b4babc2c20c8c9aa096495cd2c85d253c145561.camel@intel.com \ --to=haihao.xiang-at-intel.com@ffmpeg.org \ --cc=dmitry.v.rogozhkin@intel.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=hon.wai.chow@intel.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