Re: [PATCH v2 6/6] xen/cpupool: Allow cpupool0 to use different scheduler

[Juergen Gross <jgross@xxxxxxxx>]

On 10.03.22 18:10, Luca Fancellu wrote:
> Currently cpupool0 can use only the default scheduler, and
> cpupool_create has an harcoded behavior when creating the pool 0
Nit: s/harcoded/hardcoded/

> that doesn't allocate new memory for the scheduler, but uses the
> default scheduler structure in memory.
>
> With this commit it is possible to allocate a different scheduler for
> the cpupool0 when using the boot time cpupool.
> To achieve this the hardcoded behavior in cpupool_create is removed
> and the cpupool0 creation is moved.
>
> When compiling without boot time cpupools enabled, the current
> behavior is maintained (except that cpupool0 scheduler memory will be
> allocated).
>
> Signed-off-by: Luca Fancellu <luca.fancellu@xxxxxxx>
Reviewed-by: Juergen Gross <jgross@xxxxxxxx>


Juergen

Attachment: OpenPGP_0xB0DE9DD628BF132F.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature