mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2024-11-28 09:33:01 +00:00

History

Dennis Kempin acc162000f Add conditional compilation for unix-only crates Instead of configuring which crates to --exclude in test_config.py, we can use conditional compilation to exclude code that is not supported on windows. This allows more fine-grained control and also allows us to use plain cargo for building without complicated configuration and exclusions. BUG=b:265829867 TEST=cargo test --lib --bins --workspace --target=x86_64-pc-windows-gnu --features=all-mingw64 Change-Id: I8422c3f08053bc27d9896b220876a56bd25543d6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4165868 Reviewed-by: Vikram Auradkar <auradkar@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>		2023-01-19 21:21:59 +00:00
..
src	Add conditional compilation for unix-only crates	2023-01-19 21:21:59 +00:00
bindgen.sh	health-check: enforce blank line after copyright	2022-09-13 22:24:35 +00:00
build.rs	Add conditional compilation for unix-only crates	2023-01-19 21:21:59 +00:00
Cargo.toml	media: libva: move crc32fast to dev-dependencies	2023-01-06 17:22:56 +00:00
libva-wrapper.h	Update all copyright headers to match new style	2022-09-13 18:41:29 +00:00
README.md	Reland "Add a VAAPI wrapper crate"	2022-07-13 06:51:27 +00:00

README.md

Libva Rust wrapper

Rust wrapper for libva. Provides safe libva abstractions for use within Rust code using its own bindgen-generated bindings.

This crate is used as part of the VirtIO Video VA-API backend. VA-API uses the GPU to perform the actual decoding/encoding of frames. In doing so, it frees the CPU for other uses and reduces power usage in the system. Hardware accelerated media workflows also tend to be faster than their software counterparts.

Note: This create requires the native libva library at link time. It also requires a VA-API driver to be installed on the system. The VA-API driver to use depends on the underlying hardware, e.g.: the implementation for Intel hardware is in intel-media-driver, whereas AMD hardware will depend on Mesa.

An easy way to see whether everything is in order is to run the vainfo utility. This is usually packaged with libva-utils or as a standalone package in some distributions. vainfo will print the VA-API version, the driver string, and a list of supported profiles and endpoints, i.e.:

vainfo: VA-API version: 1.13 (libva 2.13.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.2.2 ()
vainfo: Supported profile and entrypoints
      VAProfileNone                   : VAEntrypointVideoProc
      VAProfileNone                   : VAEntrypointStats
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Simple            : VAEntrypointEncSlice
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      etc

For decoding, the desired profile must be supported under VAEntrypointVLD. For example, in order to decode VP8 media, this line must be present in the output of vainfo:

      VAProfileVP8Version0_3          : VAEntrypointVLD

Whereas to decode H264 Main profile media, this line must be present:

      VAProfileH264Main               : VAEntrypointVLD

For more information on VA-API and its usage within ChromeOS, see this guide.

For a brief introduction on how to use this crate, see the libva_utils_mpeg2vldemo test under src/lib.rs.