RE: [PATCH] VMware balloon: force compiling as a module
From: Chetan Loke
Date: Wed Jun 30 2010 - 14:43:13 EST
> From: linux-kernel-owner@xxxxxxxxxxxxxxx [mailto:linux-kernel-
> owner@xxxxxxxxxxxxxxx] 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 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?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/