From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50171) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbZlQ-0005jp-Cw for qemu-devel@nongnu.org; Tue, 07 Oct 2014 14:45:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XbZlK-0000kn-5A for qemu-devel@nongnu.org; Tue, 07 Oct 2014 14:45:36 -0400 Received: from mx1.redhat.com ([209.132.183.28]:11926) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbZlJ-0000kL-Ev for qemu-devel@nongnu.org; Tue, 07 Oct 2014 14:45:30 -0400 Message-ID: <543434BE.3060209@redhat.com> Date: Tue, 07 Oct 2014 20:45:18 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <20141002132119.GD30564@stefanha-thinkpad.redhat.com> <542D5284.1060201@suse.de> <87tx3mblhq.fsf@blackfin.pond.sub.org> <542D6127.7040308@suse.de> <87tx3ma56u.fsf@blackfin.pond.sub.org> <542D8E3C.6000207@redhat.com> <87k34c71gi.fsf@blackfin.pond.sub.org> <5433BA8E.9070101@redhat.com> <87ppe413de.fsf@blackfin.pond.sub.org> <5434035E.1040807@redhat.com> <20141007184102.GB3811@noname.redhat.com> In-Reply-To: <20141007184102.GB3811@noname.redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] IDs in QOM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: peter.maydell@linaro.org, peter.crosthwaite@xilinx.com, Anthony Liguori , Stefan Hajnoczi , qemu-devel@nongnu.org, Markus Armbruster , stefanha@redhat.com, =?windows-1252?Q?Andreas_F=E4rber?= Il 07/10/2014 20:41, Kevin Wolf ha scritto: > Is there any way to add netdevs/chardevs/devices in a non-QemuOpts way? For chardevs, yes. > I think always checking for the same allowed set of characters is the > only sane way to do things. Otherwise you end up with names that can be > used in one place, but not in another, e.g. you can create an object, > but then not delete it again using HMP. Note that deletion does not use QemuOpts, so device_del and netdev_del could delete things with funny names. > Or you can use a name for > hotplug, but not on the initial startup when the command line > configures the device. That's definitely something to be avoided. I agree. >>> > > So the "automatic arrayification" convenience feature added a property >>> > > name restriction. What makes us sure this is the last time we add name >>> > > restrictions? >> > >> > Nothing. However, does it matter, as long as the now-disallowed names >> > were not possible at all in -object/object_add? > They were possible in QMP object-add, weren't they? Yes. I think we agree that we're going to change that. Paolo