From: "Rogozhkin, Dmitry V" <dmitry.v.rogozhkin-at-intel.com@ffmpeg.org> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>, "Xiang, Haihao" <haihao.xiang@intel.com> Cc: "Chow, Hon Wai" <hon.wai.chow@intel.com> Subject: Re: [FFmpeg-devel] [PATCH] qsv: Update ffmpeg qsv_errors to recognize GPU hang Date: Mon, 25 Jul 2022 15:25:24 +0000 Message-ID: <79672d7d70ab18c1e26e0f70d7beb167671584b0.camel@intel.com> (raw) In-Reply-To: <fc5fe0edc4e9e2673d9ab7e35a1872e2b78ec956.camel@intel.com> On Mon, 2022-07-25 at 01:21 +0000, Xiang, Haihao wrote: > On Fri, 2022-07-22 at 11:06 -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. > > > > Signed-off-by: Hon Wai Chow <hon.wai.chow@intel.com> > > Signed-off-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com> > > --- > > libavcodec/qsv.c | 1 + > > libavfilter/qsvvpp.c | 1 + > > 2 files changed, 2 insertions(+) > > > > diff --git a/libavcodec/qsv.c b/libavcodec/qsv.c > > index 385b43b..55bcb6e 100644 > > --- a/libavcodec/qsv.c > > +++ b/libavcodec/qsv.c > > @@ -125,6 +125,7 @@ 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_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..7504906 100644 > > --- a/libavfilter/qsvvpp.c > > +++ b/libavfilter/qsvvpp.c > > @@ -100,6 +100,7 @@ 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_INCOMPATIBLE_AUDIO_PARAM, AVERROR(EINVAL), > > "incompatible audio > > parameters" }, > > { MFX_ERR_INVALID_AUDIO_PARAM, AVERROR(EINVAL), "invalid > > audio > > parameters" }, > > > > Could you add other missing qsv video errors or warnings too ? Yes, sure. For what I see we are missing 3 statuses returnable by mediasdk library implementations: MFX_ERR_GPU_HANG, MFX_ERR_NONE_PARTIAL_OUTPUT, MFX_ERR_REALLOC_SURFACE. Other statuses defined in mfxdefs.h are not returnable to ffmpeg level (they are internal or plugin specific stuff). I will resubmit the patch under other name with added stuff. > > 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:[~2022-07-25 15:25 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-22 18:06 Dmitry Rogozhkin 2022-07-25 1:21 ` Xiang, Haihao 2022-07-25 15:25 ` Rogozhkin, Dmitry V [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=79672d7d70ab18c1e26e0f70d7beb167671584b0.camel@intel.com \ --to=dmitry.v.rogozhkin-at-intel.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=haihao.xiang@intel.com \ --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