Repository navigation
va: add VA_SURFACE_ATTRIB_USAGE_HINT_PRIVATE - #896
Open
XinfengZhang wants to merge 1 commit into
Open
XinfengZhang wants to merge 1 commit into
XinfengZhang wants to merge 1 commit into
Conversation
Contributor
|
So this kind of surface can not be exported as DMA buffer? |
XinfengZhang
marked this pull request as ready for review
October 22, 2026 02:29
XinfengZhang
force-pushed
the
surface_opt
branch
from
October 22, 2026 02:33
952ce0b to
43eff89
Compare
There is currently no way for an application to tell the backend driver at allocation time that a surface will never leave the VA driver. The existing usage hints only describe intended uses, and the absence of VA_SURFACE_ATTRIB_USAGE_HINT_EXPORT cannot be distinguished from an application that simply did not pass a hint, so drivers must always assume the surface may later be exported and shared with other components such as compute or display. Add VA_SURFACE_ATTRIB_USAGE_HINT_PRIVATE to state that the surface is private to the VA driver and will not be exported. The driver is then free to choose a memory layout that is not shareable outside of it. The flag must not be combined with the DISPLAY or EXPORT hints, and vaExportSurfaceHandle() on such a surface fails with VA_STATUS_ERROR_INVALID_SURFACE. Drivers that do not recognize the flag may ignore it, so existing drivers keep working unchanged. Signed-off-by: Carl.Zhang <carl.zhang@intel.com>
XinfengZhang
force-pushed
the
surface_opt
branch
from
October 22, 2026 05:25
43eff89 to
b2f40a9
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There is currently no way for an application to tell the backend
driver at allocation time that a surface will never leave the VA
driver. The existing usage hints only describe intended uses, and the
absence of VA_SURFACE_ATTRIB_USAGE_HINT_EXPORT cannot be distinguished
from an application that simply did not pass a hint, so drivers must
always assume the surface may later be exported and shared with other
components such as compute or display.
Add VA_SURFACE_ATTRIB_USAGE_HINT_PRIVATE to state that the surface is
private to the VA driver and will not be exported. The driver is then
free to choose a memory layout that is not shareable outside of it.
The flag must not be combined with the DISPLAY or EXPORT hints, and
vaExportSurfaceHandle() on such a surface fails with
VA_STATUS_ERROR_INVALID_SURFACE. Drivers that do not recognize the
flag may ignore it, so existing drivers keep working unchanged.
🤖 Generated with Claude Code