Re: [PATCH v4 3/5] arm/dom0less: put dom0less feature code in a separate module

2023-11-13 Thread Michal Orzel
Hi Luca, On 13/11/2023 15:17, Luca Fancellu wrote: > > >> On 13 Nov 2023, at 11:58, Michal Orzel wrote: >> >> Hi Luca, >> >> Apart from pending question on static event channels code movement, a few >> NITs. > > Related to that, it seems to me that this part can be handled by a separate > pa

Re: [PATCH v4 3/5] arm/dom0less: put dom0less feature code in a separate module

2023-11-13 Thread Luca Fancellu
> On 13 Nov 2023, at 11:58, Michal Orzel wrote: > > Hi Luca, > > Apart from pending question on static event channels code movement, a few > NITs. Related to that, it seems to me that this part can be handled by a separate patch/serie from this one, moving code from domain_build.c to a new

Re: [PATCH v4 3/5] arm/dom0less: put dom0less feature code in a separate module

2023-11-13 Thread Michal Orzel
Hi Luca, Apart from pending question on static event channels code movement, a few NITs. On 13/11/2023 10:08, Luca Fancellu wrote: > > > Currently the dom0less feature code is mostly inside domain_build.c > and setup.c, it is a feature that may not be useful to everyone so > put the code in a d

[PATCH v4 3/5] arm/dom0less: put dom0less feature code in a separate module

2023-11-13 Thread Luca Fancellu
Currently the dom0less feature code is mostly inside domain_build.c and setup.c, it is a feature that may not be useful to everyone so put the code in a different compilation module in order to make it easier to disable the feature in the future. Move gic_interrupt_t in domain_build.h to use it wi