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

[Rich Persaud <persaur@xxxxxxxxx>]

On Jul 8, 2023, at 03:29, Luca Fancellu <luca.fancellu@xxxxxxx> wrote:
> 
>>>> 
>>>> Instead, the use case configurations should themselves be describable.
>>> 
>>> Thanks Christopher, Daniel and all!
>>> 
>>> So if I understand correctly, you are in favor if renaming Dom0less to
>>> Hyperlaunch throughout the Xen codebase? And we need a clarification of
>>> the docs/, especially docs/features/dom0less.pandoc?
>> 
>> Christopher wrote:
>>>> = Community resourcing
>> 
>> Note the pre-requisite work items for upstream Xen, listed under "Community 
>> Resourcing", to merge code for Hyperlaunch common interfaces and test cases, 
>> with docs on configuration of Hyperlaunch to deliver functionality for 
>> dom0less use cases.
> 
> Are you saying that before renaming the “dom0less” feature, we should wait 
> for it to be ported to the common code?

Why "wait"? In what timeframe do you expect dom0less to use Hyperlaunch code?

Can kernel component foo adopt the name of kernel component bar without code 
change?

Can dom0less stakeholders derive Hyperlaunch benefits without using Hyperlaunch 
code?

Rich


P.S. An intellectual property story from Cambridge, UK
https://en.wikipedia.org/wiki/Leibniz–Newton_calculus_controversy
https://www.smithsonianmag.com/history/ten-famous-intellectual-property-disputes-18521880/

"By the early 18th century, many credited the German mathematician and 
philosopher Gottfried Wilhelm Leibniz with inventing the study of calculus. 
Leibniz had, after all, been the first to publish papers on the topic in 1684 
and 1686. But when Englishman Isaac Newton published a book called Opticks in 
1704, in which he asserted himself as the father of calculus, a debate arose. 
Each of the thinkers’ respective countries wanted to stake a claim in what was 
one of the biggest advances in mathematics."