[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 1/6] xen/domain: Reduce the quantity of initialisation for system domains



On Wed, 2018-02-28 at 14:14 +0000, Andrew Cooper wrote:
>  * System domains don't need watchdog initialisation or iomem/irq
> rangesets,
>    and will not plausibly be a xenstore or hardware domain.
>  * The idle domain doesn't need scheduler initialisation (and in
> particular,
>    removing this path allows for substantial scheduler cleanup), and
> isn't
>    liable to ever need late_hwdom_init().
> 
> Move all of these initialisations pass the DOMCRF_dummy early exit,
> and into
> non-idle paths.  rangeset_domain_initialise() remains because it
> makes no
> allocations, but does initialise a linked list and spinlock.  The
> poolid
> parameter can be dropped as sched_init_domain()'s parameter is now
> unconditionally 0.
> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
>
Reviewed-by: Dario Faggioli <dfaggioli@xxxxxxxx>

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.