From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=35444 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PJ3Q6-0000Vl-R0
	for qemu-devel@nongnu.org; Thu, 18 Nov 2010 07:16:55 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1PJ3Q5-0008J8-QE
	for qemu-devel@nongnu.org; Thu, 18 Nov 2010 07:16:54 -0500
Received: from mx1.redhat.com ([209.132.183.28]:60751)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1PJ3Q5-0008J2-Ck
	for qemu-devel@nongnu.org; Thu, 18 Nov 2010 07:16:53 -0500
Date: Thu, 18 Nov 2010 14:16:51 +0200
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] add hotplug opt-out option for devices.
Message-ID: <20101118121651.GL7948@redhat.com>
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>
	<4CE51714.6070303@msgid.tls.msk.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4CE51714.6070303@msgid.tls.msk.ru>
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: Michael Tokarev <mjt@tls.msk.ru>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org

On Thu, Nov 18, 2010 at 03:07:48PM +0300, Michael Tokarev wrote:
> 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 ;)
> 
Don't care about name.

--
			Gleb.