From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58576) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1e3O-0000Eg-7i for qemu-devel@nongnu.org; Fri, 10 Jan 2014 10:31:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W1e3H-0001nx-Pu for qemu-devel@nongnu.org; Fri, 10 Jan 2014 10:31:22 -0500 Received: from mx1.redhat.com ([209.132.183.28]:25802) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1e3H-0001nm-GM for qemu-devel@nongnu.org; Fri, 10 Jan 2014 10:31:15 -0500 Date: Fri, 10 Jan 2014 16:31:08 +0100 From: Igor Mammedov Message-ID: <20140110163108.7a70ced0@nial.usersys.redhat.com> In-Reply-To: <20140110122810.7d34b120@thinkpad> References: <1389197382-25085-1-git-send-email-imammedo@redhat.com> <52CD7BBF.3030202@redhat.com> <20140108175159.029e5f9e@nial.usersys.redhat.com> <52CD8BD7.8070706@redhat.com> <20140110122810.7d34b120@thinkpad> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC 0/5] -object/object-add support custom location and 2nd stage initialization List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Igor Mammedov Cc: aliguori@amazon.com, sw@weilnetz.de, mjt@tls.msk.ru, qemu-devel@nongnu.org, lcapitulino@redhat.com, blauwirbel@gmail.com, stefanha@redhat.com, Paolo Bonzini , afaerber@suse.de, rth@twiddle.net On Fri, 10 Jan 2014 12:28:10 +0100 Igor Mammedov wrote: > On Wed, 08 Jan 2014 18:33:11 +0100 > Paolo Bonzini wrote: > > > Il 08/01/2014 17:51, Igor Mammedov ha scritto: [...] > > > The reason for separate interfaces is that realize interface is more generic > > > and might be used outside of '-object'. While I don't see 'path' interface > > > ever used outside of -object. > > > > Yeah, I think the two interfaces are a good idea. The question is > > whether we want the second interface at all. I think it's fine to > > delegate namespace conventions to management. > with dropping it, backends for sure can work without it, they will be just > placed directly under "/objects". For memdev backend it might be upto 256 > objects, clattering "/objects" container. > Stefan had the similar idea about grouping iothread objects inside > "/backends/iothreads". so what do we do with PATH interface? 1. drop it and put all backends into '/objects' container 2. keep it, allowing QEMU set default namespace 3. as discussed in "autogenerate ID" thread let management to pass QOM path as ID and in case it starts with '/' use provided QOM path and default to '/object' for not path ID. > > Paolo > >