From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:52086)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1R4GFy-000885-1g
	for qemu-devel@nongnu.org; Thu, 15 Sep 2011 14:01:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1R4GFs-0005eB-4q
	for qemu-devel@nongnu.org; Thu, 15 Sep 2011 14:01:50 -0400
Received: from mail-yi0-f45.google.com ([209.85.218.45]:34146)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1R4GFs-0005e0-14
	for qemu-devel@nongnu.org; Thu, 15 Sep 2011 14:01:44 -0400
Received: by yib2 with SMTP id 2so2842429yib.4
	for <qemu-devel@nongnu.org>; Thu, 15 Sep 2011 11:01:43 -0700 (PDT)
Message-ID: <4E723D84.60504@codemonkey.ws>
Date: Thu, 15 Sep 2011 13:01:40 -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>
	<4E722A22.70700@siemens.com>
In-Reply-To: <4E722A22.70700@siemens.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: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Peter Maydell <peter.maydell@linaro.org>, Gerd Hoffmann <kraxel@redhat.com>, Markus Armbruster <armbru@redhat.com>, "Edgar E. Iglesias" <edgar.iglesias@gmail.com>

On 09/15/2011 11:38 AM, Jan Kiszka wrote:
> On 2011-09-15 16:11, Anthony Liguori wrote:
>> 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.
>
> One of the many paths is still "<unique-nic-name>/nvram", so nothing
> changed.
>
> Auto-generated names are not needed, just use paths. In the end a device
> name is a path as well, one with only a single element.

The auto-generated name right now would be:

"<unique-nic-name>::nvram"

You are right that that is also a path.  And I now think you are right that we 
could just s|::|/|g and declare that names are paths.

The only problem with this is it introduces a canonical path format.  That may 
or may not be a bad thing..

Regards,

Anthony Liguori