[Libva] How to detect the type of memory returned...

[Jean-Yves Avenard]

On 22 June 2014 19:06, Jean-Yves Avenard <jyavenard at gmail.com> wrote:
> Hi
>
> On 18 June 2014 13:22, Xiang, Haihao <haihao.xiang at intel.com> wrote:
>>
>> Yes, The buffer for vaGetImage() will be mapped to
>> USWC memory too after applying the patch.
>>
>
> Ok.. here are my results.
>
> I've timed the fo
> Without the patch, the copy routine detects that using memcpy is
> faster than using SSE4 code and as such copy uses memcpy.
> With the patch, copy uses SSE4 code as it's faster than memcpy. So
> this indeed confirms it's USWC memory
>

should have added:
$ vainfo
libva info: VA-API version 0.35.1
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/local/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_35
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.35 (libva 1.3.1)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 1.3.2
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :    VAEntrypointVLD
      VAProfileMPEG2Simple            :    VAEntrypointEncSlice
      VAProfileMPEG2Main              :    VAEntrypointVLD
      VAProfileMPEG2Main              :    VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline:    VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:    VAEntrypointEncSlice
      VAProfileH264Main               :    VAEntrypointVLD
      VAProfileH264Main               :    VAEntrypointEncSlice
      VAProfileH264High               :    VAEntrypointVLD
      VAProfileH264High               :    VAEntrypointEncSlice
      VAProfileVC1Simple              :    VAEntrypointVLD
      VAProfileVC1Main                :    VAEntrypointVLD
      VAProfileVC1Advanced            :    VAEntrypointVLD
      VAProfileNone                   :    VAEntrypointVideoProc
      VAProfileJPEGBaseline           :    VAEntrypointVLD

using libva and drivers from release (not git master)