Re: [Xen-devel] [PATCH v2 4/5] tools: xenpm: continue to support {set, get}-vcpu-migration-delay

Il 28 Feb 2018 17:03, "George Dunlap" ha scritto: > Again, I considered this, for that same reason. The reason why I > decided for stdout is for maximizing the chances that anyone actually > using this will see the warning (even if, e.g., they're redirecting > stderr).

Re: [Xen-devel] [PATCH v2 4/5] tools: xenpm: continue to support {set, get}-vcpu-migration-delay

On 02/28/2018 03:17 PM, Dario Faggioli wrote: > On Wed, 2018-02-28 at 15:02 +, George Dunlap wrote: >> On 02/23/2018 04:41 PM, Dario Faggioli wrote: >>> From this commit on, `xenpm {set,get}-vcpu-migration-delay' >>> >>> commands work again. But that is only for the sake of >>> backward

Re: [Xen-devel] [PATCH v2 4/5] tools: xenpm: continue to support {set, get}-vcpu-migration-delay

On Wed, 2018-02-28 at 15:02 +, George Dunlap wrote: > On 02/23/2018 04:41 PM, Dario Faggioli wrote: > > From this commit on, `xenpm {set,get}-vcpu-migration-delay' > > > > commands work again. But that is only for the sake of > > backward compatibility, and their use is deprecated, in > >

Re: [Xen-devel] [PATCH v2 4/5] tools: xenpm: continue to support {set, get}-vcpu-migration-delay

On 02/23/2018 04:41 PM, Dario Faggioli wrote: > Now that it is possible to get and set the migration > delay via the SCHEDOP sysctl, use that in xenpm, instead > of the special purpose libxc interface (which will be > removed in a following commit). > > The sysctl, however, requires a cpupool-id

[Xen-devel] [PATCH v2 4/5] tools: xenpm: continue to support {set, get}-vcpu-migration-delay

Now that it is possible to get and set the migration delay via the SCHEDOP sysctl, use that in xenpm, instead of the special purpose libxc interface (which will be removed in a following commit). The sysctl, however, requires a cpupool-id argument, for knowing on which scheduler it is operating