linux-kernel - Re: [PATCH 4/4] Add VMware memory balloon driver

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4BA4C961.9060006@redhat.com>
Date:	Sat, 20 Mar 2010 15:10:57 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Dmitry Torokhov <dtor@...are.com>
CC:	linux-kernel@...r.kernel.org, pv-drivers@...are.com,
	Alok Kataria <akataria@...are.com>,
	Saileshkumar Jain <sajain@...are.com>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH 4/4] Add VMware memory balloon driver

On 03/19/2010 10:47 PM, Dmitry Torokhov wrote:
> This is a virtio-based transport between VMware's hypervisor
> and virtio_ballon driver that allows host control guest memory
> ballooning.
>
>    

This is a little wierd since it's specific to the balloon driver.  The 
virtio design is to make transport and device orthogonal so we could 
mix'n'match any driver with any transport, but this will only work with 
the balloon driver.  It's also 640 lines while the original balloon 
driver is ~300.  Some of that is because you're emulating a queue that 
doesn't really exist, IIUC.

So while I'd love to see other hypervisors adopt virtio, I think in this 
case it makes more sense to have your own balloon driver.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

--
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/