-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new error code to indicate the reset happended in the driver. #714
Add new error code to indicate the reset happended in the driver. #714
Conversation
347520e
to
e04fe6d
Compare
Hi, @XinfengZhang @Jexu, could you pls help to review this PR? |
d7d0421
to
f18f2d5
Compare
* After the applications get VA_STATUS_HW_BUSY or VA_STATUS_SUCCESSFULL from vaSyncSurface(), | ||
* it still can call vaQuerySurfaceError to find out further details to know if has real hw reset | ||
* happened on this surface since umd and kmd could recover the context from reset with success in sometimes. | ||
* VA_STATUS_HW_BUSY or VA_STATUS_SUCCESSFULL also could be passed in as "error_status". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if there are one reset, and after re-run a while, there are another reset. how to know it?
each frame I need call it, first frame it is VADecodeReset, next frames it is invalid, then VADecodeReset again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If user wants to know all the reset frames, then user needs to call vaQuerySurfaceError() for every frame and recode the reset information.
If user don't care about the reset, he can just call vaQuerySurfaceError() when get error from syncSurface().
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, even "success" is treated as "error code" , it looks a little tricky.
Use VADecodeReset to indeicate media reset/engine reset have happended in the driver, user can use vaQuerySurfaceError() to get the detail info to do some customized work. Signed-off-by: Pengxin, Yuan <[email protected]>
f18f2d5
to
dcf353c
Compare
Use VA_STATUS_ERROR_RESET to indeicate media reset/engine reset have happended in the driver, user can use vaQuerySurfaceError() to get the detail info to do some customized work.