linux-kernel - [RFC/PATCH 0/4] VMware balloon driver over virtio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 19 Mar 2010 13:46:41 -0700
From:	Dmitry Torokhov <dtor@...are.com>
To:	linux-kernel@...r.kernel.org
Cc:	pv-drivers@...are.com, Alok Kataria <akataria@...are.com>,
	Saileshkumar Jain <sajain@...are.com>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: [RFC/PATCH 0/4] VMware balloon driver over virtio

Hi,

VMware would like to get its Linux balloon driver merged into mainline
and is considering doing it within virtio framework.

The following is the initial implementation of our ballooning interface
as a virtio device. It allows our hypervisor to work in tandem with
virtio_balloon driver and inflate and deflate balloon on demand.

Due to the fact that our monitor works a bit differently from KVM some
changes are needed in virtio_balloon itself, namely:

- our hypervisor may refuse locking certain pages. This may happen,
  for example, when target balloon size is changed since guest polled
  it last time. We expect guest to try locking different page and
  release refused pages once target balloon size is reached.

- our hypervisor may, in certain situations, reset the balloon. In this
  case it expects guest to quickly release all memory allocated by
  by the balloon but to not bother telling the host about pages being
  released.

There are more differences (adaptive allocation rates, sleeping
allocations) which we intend to address at a later date if it is
decided that virtio is the proper subsystem to be used for our
driver.

Thanks!

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/