On Fri, 2019-09-27 at 09:00 +0200, Juergen Gross wrote: > On- and offlining cpus with core scheduling is rather complicated as > the cpus are taken on- or offline one by one, but scheduling wants > them > rather to be handled per core. > > As the future plan is to be able to select scheduling granularity per > cpupool prepare that by storing the granularity in struct cpupool and > struct sched_resource (we need it there for free cpus which are not > associated to any cpupool). Free cpus will always use granularity 1. > > Store the selected granularity option (cpu, core or socket) in the > cpupool as well, as we will need it to select the appropriate cpu > mask > when populating the cpupool with cpus. > > This will make on- and offlining of cpus much easier and avoids > writing code which would needed to be thrown away later. > > Move the granularity related variables to cpupool.c as they are now > used form there only. > > Signed-off-by: Juergen Gross <[email protected]> > Reviewed-by: Dario Faggioli <[email protected]>
Regards -- Dario Faggioli, Ph.D http://about.me/dario.faggioli Virtualization Software Engineer SUSE Labs, SUSE https://www.suse.com/ ------------------------------------------------------------------- <<This happens because _I_ choose it to happen!>> (Raistlin Majere)
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
