linux-kernel - RE: [PATCH] VMware balloon: force compiling as a module

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]

Message-ID: <AANLkTimmIG6GF-hKBk7JsZpvZNEAj1Tlt4GrPXexN0_0@mail.gmail.com>
Date:	Wed, 30 Jun 2010 14:42:53 -0400
From:	Chetan Loke <chetanloke@...il.com>
To:	dtor@...are.com, pv-drivers@...are.com
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	akpm@...ux-foundation.org, chetanloke@...il.com
Subject: RE: [PATCH] VMware balloon: force compiling as a module

> From: linux-kernel-owner@...r.kernel.org [mailto:linux-kernel-
> owner@...r.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
--
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/