Messages in this thread | | | Date | Wed, 30 Jun 2010 14:42:53 -0400 | Subject | RE: [PATCH] VMware balloon: force compiling as a module | From | Chetan Loke <> |
| |
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel- > owner@vger.kernel.org] On Behalf Of Dmitry Torokhov > Sent: June 28, 2010 7:01 PM > VMware Tools installer requires the upstream driver to be compiled > as a module in order to detect its presence and avoid installing > our own version on top of it. To avoid surprises with 2 versions > of the driver being installed and fighting with each other, let's > force the driver to be compiled as a module unless user selects > CONFIG_EMBEDDED. >
> config VMWARE_BALLOON > tristate "VMware Balloon Driver" > - depends on X86 > + depends on X86 && (EMBEDDED || m)
None of the following questions are related to this patch.
Q1)Does vmtools handle pvscsi correctly?
Q2)In case if a VM wants to be a good citizen, is there a way for a guest to know about the balloon-event?
Q3)What if an app mlock's its memory resources and driver's have pinned down their pages then how does inflation work?
regards Chetan Loke
| |