From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=57986 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PJ3HN-0000ZY-O9
	for qemu-devel@nongnu.org; Thu, 18 Nov 2010 07:07:54 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mjt@tls.msk.ru>) id 1PJ3HM-0006TN-HH
	for qemu-devel@nongnu.org; Thu, 18 Nov 2010 07:07:53 -0500
Received: from isrv.corpit.ru ([86.62.121.231]:45717)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mjt@tls.msk.ru>) id 1PJ3HM-0006T5-9d
	for qemu-devel@nongnu.org; Thu, 18 Nov 2010 07:07:52 -0500
Message-ID: <4CE51714.6070303@msgid.tls.msk.ru>
Date: Thu, 18 Nov 2010 15:07:48 +0300
From: Michael Tokarev <mjt@tls.msk.ru>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 0/3] add hotplug opt-out option for devices.
References: <1290077118-11577-1-git-send-email-kraxel@redhat.com>	<20101118110113.GE7948@redhat.com>
	<4CE50A51.1080209@redhat.com>	<20101118112043.GG7948@redhat.com>
	<4CE50E03.1020907@redhat.com> <20101118114225.GH7948@redhat.com>
In-Reply-To: <20101118114225.GH7948@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gleb Natapov <gleb@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org

On 18.11.2010 14:42, Gleb Natapov wrote:
[]
>> For *that* use case well have to do a bit more like dynamically
>> building the acpi table which indicates which slots are
>> hot-pluggable and which are not.  Which indeed would be useful and
>> would fix the windows xp offering me to unplug the piix chipset in
>> the "savely remove hardware" menu ;)
>>
> Yes, but management has to specify to us somehow that certain device
> is not hotpluggable and notunplug=no looks like good way to do it.

Can we _please_ get rid of this double negative and specify
it as usual hotplug={on|off} ? :)  It does not matter if in
the code it will be called nohotplug, the parameter parser
function can perform the necessary negation.  nohotplug=no
is just plain wrong ;)

/mjt