[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC PATCH] xen/arm: Rebranding dom0less feature



Hi Luca,

On Jun 30, 2023, at 05:12, Luca Fancellu <luca.fancellu@xxxxxxx> 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:

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: 

2023 Hyperlaunch design session last week, thanks to Apertus and AMD:

Signed-off-by: Luca Fancellu <luca.fancellu@xxxxxxx>

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.