On Tue, 2017-01-24 at 13:35 +0100, Juergen Gross wrote: > On 23/01/17 15:40, George Dunlap wrote: > > > > Having a "cpupool-remove" operation that doesn't actually remove > > the > > cpu from the pool is a bit mad... > > Logically it does remove the cpu from Pool-0. It is just that there > is > no other scheduler entity involved for doing so. > Yes, it's removed from the pool, *but* it basically remains part of the pool's scheduler, that's the issue.
As you say, there's no another scheduler to which we can attach it... So, as of now, I see two options: 1) create such (dummy) scheduler; 2) go all the way down toward deallocating the scheduler related data of the cpu (and reallocate them back when re-added). BTW, Anshul also hit this problem while also doing some work on Credit2, and told me he'd be giving some thinking to it, and try to figure some ideas out (as soon as he'd be free of a couple of other burdens :-D). Let's see what he'll come up with. :-) Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
