Hi Luca, On Jun 30, 2023, at 05:12, Luca Fancellu <luca.fance...@arm.com> wrote: > > The "dom0less" feature was intended to be the feature where a domU > domain could be launched without the control domain (Dom0) > intervention, however the name seems to suggest that Dom0 cannot > be part of the configuration, while instead it's a possible use case.
Thanks for your interest in Xen boot integrity. Please see the 2018 domB RFC: https://lists.xenproject.org/archives/html/xen-devel/2018-06/msg01306.html At Xen Summit 2018 (Nanjing) and Xen Summit 2019 (Chicago), OpenXT contributors made a case to Xen-on-Arm contributors for the architectural unification of incumbent dom0less (Arm) and the domB (x86) proposal for improving Xen boot integrity. > To avoid that, rename the "dom0less" configuration with the name > "hyperlaunch", that is less misleading. 2018-2022 work on Xen launch integrity, thanks to Apertus and Star Lab: https://wiki.xenproject.org/wiki/Hyperlaunch https://www.theregister.com/2022/12/16/xen_4_17_hyperlaunch/ 2023 Hyperlaunch design session last week, thanks to Apertus and AMD: https://lists.xenproject.org/archives/html/xen-devel/2023-06/msg01870.html > Signed-off-by: Luca Fancellu <luca.fance...@arm.com> If Arm is now ready to invest engineering resources into new Xen launch integrity features for security and safety-critical use cases, that is exciting news, 5 years into the on-again-off-again bootstrapped Hyperlaunch project! The roadmap would benefit from new funding. Would you like to attend the next Xen working group call for Hyperlaunch? Rich
