Separate VSM/VTL features from LVBS platform
Open
@sangho2 is already working on this.
Since Jul 15, 2025.
enhancement
target-lvbs
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
Currently, we implement most of VSM and VTL features inside the LiteBox LVBS platform which is not ideal given that these features are largely independent from the LiteBox platform. Instead, it would better to separate these VSM and VTL features from the platform and incorporate them into the LVBS runner (e.g., place the VTL1 event loop inside the runner). This would be also helpful to implement the OP-TEE Shim while not introducing any other unnecessary punch throughs between the OP-TEE Shim and the LVBS platform.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.