From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:33736)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1R4Y1l-00057L-HV
	for qemu-devel@nongnu.org; Fri, 16 Sep 2011 09:00:29 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1R4Y1g-0008Gw-Pc
	for qemu-devel@nongnu.org; Fri, 16 Sep 2011 09:00:21 -0400
Received: from mail-yx0-f173.google.com ([209.85.213.173]:38562)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1R4Y1g-0008Gr-Mk
	for qemu-devel@nongnu.org; Fri, 16 Sep 2011 09:00:16 -0400
Received: by yxl11 with SMTP id 11so3521140yxl.4
	for <qemu-devel@nongnu.org>; Fri, 16 Sep 2011 06:00:15 -0700 (PDT)
Message-ID: <4E73485C.8090607@codemonkey.ws>
Date: Fri, 16 Sep 2011 08:00:12 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
References: <4E70EC90.8000904@us.ibm.com>	<4E7100E9.70305@web.de>	<4E7103AE.5060201@codemonkey.ws>	<4E711969.8030400@web.de>	<4E71267A.3020808@codemonkey.ws>
	<4E720103.7040100@siemens.com>	<4E72079D.5060103@codemonkey.ws>
	<4E7320F1.1020905@redhat.com>
In-Reply-To: <4E7320F1.1020905@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC] Plan for moving forward with QOM
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/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: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>, Markus Armbruster <armbru@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>, "Edgar E. Iglesias" <edgar.iglesias@gmail.com>

On 09/16/2011 05:12 AM, Kevin Wolf wrote:
> Am 15.09.2011 16:11, schrieb Anthony Liguori:
>> An example is a NIC with nvram that stores a mac address.  In QOM, the guest
>> could change the mac address, then a user could hot unplug the device, and then
>> hot plug the device into a different PCI slot.  The path is now different but
>> the device name has not change.
>
> Maybe then the device name shouldn't default to something that looks
> like a path but rather something like "#foo-1" where "foo" is a device
> name and "1" a counter for devices of the same type (I'm reusing Jan's #
> notation in order to avoid clashes with user specified names, but that's
> a detail). I guess a name like that would actually be relatively
> convenient to use from a user interface like HMP.

Yeah, I was thinking about this myself yesterday.  To avoid confusion, we could 
just make the names more or less random.  That would ensure that no one used 
them directly.

I would expect people to use paths in HMP.  A nice advantage of paths is that 
you can autocomplete them in HMP.

Regards,

Anthony Liguori

>
> Kevin
>