> On 1 Jul 2023, at 08:53, Andrew Cooper <andrew.coop...@citrix.com> wrote:
> 
> On 30/06/2023 10:12 am, Luca Fancellu 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.
>> 
>> To avoid that, rename the "dom0less" configuration with the name
>> "hyperlaunch", that is less misleading.
>> 
>> Signed-off-by: Luca Fancellu <luca.fance...@arm.com>
>> ---
>> This is an RFC to get the feeling of the community about the name
>> change, for now it's everything in one patch just to see how it
>> will look like, if there is interest on proceeding into it, I can
>> split in more commit.
> 
> Have you discussed this with Dan and Chris at all?  You haven't even
> CC'd them.

No, this rename idea started from a chat during the summit, anyway Julien
promptly add them to the CC, because I forgot.

> 
> While there is a lot of end-goal in common between the dom0less and
> hyperlaunch, and that the name dom0less is deeply misleading,
> hyperlaunch is specifically not this.

Yes Hyperlaunch is more than this, however as I said, with this RFC I would like
to ear opinions, @Daniel @Christopher could it be a proper name for the dom0less
feature?

If this patch makes things more difficult for the Hyperlunch serie, I’m ok to 
drop it,
my only aim was just to find a less misleading name for the feature. 

Cheers,
Luca

> 
> ~Andrew

Reply via email to