From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MGGbp-0007TV-BF for qemu-devel@nongnu.org; Mon, 15 Jun 2009 14:08:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MGGbk-0007Qz-HO for qemu-devel@nongnu.org; Mon, 15 Jun 2009 14:08:40 -0400 Received: from [199.232.76.173] (port=36424 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MGGbk-0007Qt-Cy for qemu-devel@nongnu.org; Mon, 15 Jun 2009 14:08:36 -0400 Received: from mx2.redhat.com ([66.187.237.31]:44526) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MGGbj-0007CG-SV for qemu-devel@nongnu.org; Mon, 15 Jun 2009 14:08:36 -0400 Subject: Re: [Qemu-devel] Re: [PATCH] Add -no-virtio-balloon command-line option References: <1244661817-3293-1-git-send-email-ehabkost@redhat.com> <4A300891.4060500@codemonkey.ws> <20090610193408.GE18045@blackpad> <4A30D748.8070507@redhat.com> <4A36138C.4060306@redhat.com> <87vdmx69na.fsf@pike.pond.sub.org> <4A36447B.6030509@codemonkey.ws> From: Markus Armbruster Date: Mon, 15 Jun 2009 20:07:42 +0200 In-Reply-To: <4A36447B.6030509@codemonkey.ws> (Anthony Liguori's message of "Mon\, 15 Jun 2009 07\:54\:19 -0500") Message-ID: <87ab49z7yp.fsf@pike.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org Anthony Liguori writes: > Markus Armbruster wrote: >> Dor Laor writes: >> >> >>> Gerd Hoffmann wrote: >>> >>>>> This new option may be used to disable the virtio-balloon device. >>>>> >>>>> >>>> ACK, looks good. >>>> >>>> And I can drop my lazy patch which just comments out virtio-balloon >>>> in the code ;) >>>> >>> Actually, I rather have the balloon disabled by default. It's like any >>> other pci device which needs >>> explicit command line specification. Why consume a pci slot if not >>> implicitly required? >>> >> >> I agree. The command line is plenty magic without implicitly added >> PCI devices. >> >> Besides, negative options -no-virtio-balloon lead to ugly >> double-negatives like if (!no_virtio_balloon). >> > > It does no harm to add the device by default so why force the user to > explicitly enable it? > > Regards, > > Anthony Liguori I don't care whether it's on or off by default. I just object to the ugly -no-virtio-balloon. We need to do (at least) two things to the virtio-balloon device: suppress it, and control its PCI address. We can do both with one option, but it better not be called -no-virtio-balloon then. Options controlling devices should always be extensible to accept arbitrary name=value arguments.