mirror of
https://github.com/cloud-hypervisor/cloud-hypervisor.git
synced 2024-07-02 16:02:37 +00:00
1795afadb8
By factorizing the algorithm untangling TDVF sections from guest RAM into a dedicated function, we can write some unit tests to validate it properly achieves what we expect. Adding the "tdx" feature to the unit tests, otherwise it wouldn't get tested. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
25 lines
704 B
Bash
Executable File
25 lines
704 B
Bash
Executable File
#!/bin/bash
|
|
|
|
source $HOME/.cargo/env
|
|
source $(dirname "$0")/test-util.sh
|
|
|
|
process_common_args "$@"
|
|
|
|
BUILD_TARGET=${BUILD_TARGET-x86_64-unknown-linux-gnu}
|
|
cargo_args=("")
|
|
|
|
if [[ $hypervisor = "mshv" ]]; then
|
|
cargo_args+=("--no-default-features")
|
|
cargo_args+=("--features common,$hypervisor")
|
|
elif [[ $(uname -m) = "x86_64" ]]; then
|
|
cargo_args+=("--features tdx")
|
|
fi
|
|
|
|
if [[ "${BUILD_TARGET}" == "aarch64-unknown-linux-musl" ]]; then
|
|
export TARGET_CC="musl-gcc"
|
|
export RUSTFLAGS="-C link-arg=-lgcc -C link_arg=-specs -C link_arg=/usr/lib/aarch64-linux-musl/musl-gcc.specs"
|
|
fi
|
|
|
|
export RUST_BACKTRACE=1
|
|
cargo test --lib --bins --target $BUILD_TARGET --workspace ${cargo_args[@]} || exit 1
|