Re: [PATCH v6 4/7] xen/arm: configure dom0less domain for enabling xenstore after boot

[Julien Grall <julien@xxxxxxx>]

On 11/05/2022 16:05, Rahul Singh wrote:
> > > The property "xen,enhanced" with an empty string (or with the value "enabled") 
> > > is meant to indicate that PV drivers will be usable in the domain.
> > >
> > > AFAIU, you are suggesting to change the meaning based on dom0 whether has been 
> > > created. I don't particularly like that because a user may spent a while to 
> > > understand why Xenstored doesn't work.
> > >
> > > The current proposal for xen,enhanced allows us to define new values if we 
> > > wanted to only enabled selected interfaces. AFAIU, in your case, you only want 
> > > to expose the event channel interface, so I would create a new value to 
> > > indicate that the event channel interface is exposed. Xen would then create 
> > > only the part for the event channel (i.e. no extended regions, grant tables...).
> > Ok. I will create the new property something like “xen,evtchn” to enable the 
> > event-channel for dom0less guests.
> > Based on “xen,evtchn” property I will create the hypervisor node with only PPI 
> > interrupt property.
> If we don’t want to create the new property we can use "xen,enhanced = evtchn” 
> to
> enable the event-channel interfacefor dom0less guests.
I would prefer the "xen,enhanced = evtchn" because to avoid corner cases 
such as xen,enhanced without xen,evtchn
Cheers,

--
Julien Grall