enable memory location query and set#601
Conversation
| * Image flags , app could retrieve surface informations by this flag after calling vaDeriveImage | ||
| * the flags could include the memory location/region etc. | ||
| * bit0 = 1: the flags is valid flags | ||
| * bit1-2: memory location: 0 system memeory, 1 local memory. |
There was a problem hiding this comment.
So, which bit is for system memory and which for local? did you intent to have bit1 only here?
There was a problem hiding this comment.
bit 1 -2 represent 2bit values, if bit0 is valid, then bit1 is 0 represent system memory, bit1 is 1 represent local memory, bit 2 is used for future, I will update it.
| * bit0 = 1: the flags is valid flags | ||
| * bit1-2: memory location: 0 system memeory, 1 local memory. | ||
| */ | ||
| uint32_t flags; |
There was a problem hiding this comment.
Can we introduce some bit masks to help users understand what's going on?
| * bit0 = 1: the flags is valid flags | ||
| * bit1-2: memory location: 0 system memeory, 1 local memory. | ||
| */ | ||
| uint32_t flags; |
There was a problem hiding this comment.
Do we really need add this "flags" member in VAImage, since we can query memory region info through surfaceattributes (e.g., surface_attrib.value.value.i) ?
There was a problem hiding this comment.
the problem is we could not get surfaceattributes for one dedicate surface
7488f49 to
d32f999
Compare
1. app could specify the memory location by vaCreateSurfaces 2. app could query the memory regions supported by backend driver 3. app could query the surface memory location by vaDeriveImage Signed-off-by: XinfengZhang <carl.zhang@intel.com>
d32f999 to
10853eb
Compare
1. it need definitions in intel/libva#601 2. default behavior is determined by driver (local memory prefered) 3. it will be impacted by platform WA such as WaForceAllocateLML3 Signed-off-by: Carl Zhang <carl.zhang@intel.com>
it need definitions in intel/libva#601 Signed-off-by: Carl Zhang <carl.zhang@intel.com>
1. it need definitions in intel/libva#601 2. default behavior is determined by driver (local memory prefered) 3. it will be impacted by platform WA such as WaForceAllocateLML3 Signed-off-by: Carl Zhang <carl.zhang@intel.com>
it need definitions in intel/libva#601 Signed-off-by: Carl Zhang <carl.zhang@intel.com>
Signed-off-by: XinfengZhang carl.zhang@intel.com