Arm backend: Add VGF check environment#19911
Conversation
Signed-off-by: Elena Zhelezina <elena.zhelezina@arm.com> Change-Id: I02b655802bcc9b76423d76e7fa3d7e17086dafd7
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19911
Note: Links to docs will display an error until the docs builds have been completed. This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@digantdesai Could you please review this PR ? |
|
@wwwind the added files might be needed to be added the buck2 files? |
| _check_tosa_serializer(), | ||
| _check_model_converter(), | ||
| _check_model_converter_lib_dir(), |
There was a problem hiding this comment.
This is OK, but I would prefer these to be naturally in the the dependent python module, as opposed to a seperate script. The rationale is now someone has to make sure that this script and actual consumers are always in sync, i.e. you don't want to be in a situation where this scripts says check passes but the actual user fails because the new dep isn't part of the sync, for example.
digantdesai
left a comment
There was a problem hiding this comment.
Stamping to unblock.
|
Arm smaller_stories_llama fail is known and unrelated and beeing worked on |
The VGF backend provides a preflight helper that can be run before export or runtime execution: ```bash python -m executorch.backends.arm.vgf.check_env --aot python -m executorch.backends.arm.vgf.check_env --runtime python -m executorch.backends.arm.vgf.check_env --host-emulator python -m executorch.backends.arm.vgf.check_env --source-build --build-dir cmake-out ``` Use `--aot` before export. It checks that the TOSA serializer and ML SDK model converter are available and that the converter can be launched. Use `--runtime` when debugging Python runtime availability. It checks whether the ExecuTorch runtime backend registry reports VgfBackend as available. Use `--host-emulator` before host-based emulator runs. It checks runtime availability plus Vulkan SDK and ML emulation layer environment variables. Use `--source-build --build-dir <dir>` when debugging a source build. It checks for VGF runtime build prerequisites such as `libvgf` and CMake options including `EXECUTORCH_BUILD_VGF` and `EXECUTORCH_BUILD_VULKAN`. For CI logs or bug reports, add `--json`: ```bash python -m executorch.backends.arm.vgf.check_env --aot --json ``` cc @digantdesai @freddan80 @per @zingo @oscarandersson8218 @mansnils @Sebastian-Larsson @robell @rascani --------- Signed-off-by: Elena Zhelezina <elena.zhelezina@arm.com>
The VGF backend provides a preflight helper that can be run before export or runtime execution:
Use
--aotbefore export. It checks that the TOSA serializer and ML SDK model converter are available and that the converter can be launched.Use
--runtimewhen debugging Python runtime availability. It checks whether the ExecuTorch runtime backend registry reports VgfBackend as available.Use
--host-emulatorbefore host-based emulator runs. It checks runtime availability plus Vulkan SDK and ML emulation layer environment variables.Use
--source-build --build-dir <dir>when debugging a source build. It checks for VGF runtime build prerequisites such aslibvgfand CMake options includingEXECUTORCH_BUILD_VGFandEXECUTORCH_BUILD_VULKAN.For CI logs or bug reports, add
--json:cc @digantdesai @freddan80 @per @zingo @oscarandersson8218 @mansnils @Sebastian-Larsson @robell @rascani