On Thu, Feb 06, 2014 at 11:58:34AM -0500, Konrad Rzeszutek Wilk wrote:
> On February 6, 2014 8:12:55 AM EST, Daniel Kiper <> wrote:
[...]
> >Maybe we should not built in any complexity in balloon driver itself.
> >Hence it should be just simple get/put pages from balloon device (with
> >option to hotplug memory in the future). However, host and guest (maybe
> >it should be configured at boot?) should provide knobs (via sysfs, ioctl,
> >...?) to drive balloon device/driver. This way anybody could build
> >separate process/module with required logic and policies. There is one but...
> >Such idea was once implemented in Xen by Dan Magenheimer (look for
> >tools/xenballoon in Xen 4.2) but later it was dropped. I do not why.
> >So I am CC-ing Bob and Konrad who may know more about that.
>
> Because the xen-self-balloon driver does it and there were no need
> for an userspace tool to do the same thing.
OK but why it was decided to move this functionality from userspace
to kernel driver?
Daniel
