From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36289) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKSGV-0004FG-RM for qemu-devel@nongnu.org; Mon, 03 Mar 2014 07:46:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WKSGN-0000Sq-Di for qemu-devel@nongnu.org; Mon, 03 Mar 2014 07:46:39 -0500 Received: from mail-qc0-x22f.google.com ([2607:f8b0:400d:c01::22f]:61696) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKSGN-0000Sj-8n for qemu-devel@nongnu.org; Mon, 03 Mar 2014 07:46:31 -0500 Received: by mail-qc0-f175.google.com with SMTP id e16so3606222qcx.20 for ; Mon, 03 Mar 2014 04:46:30 -0800 (PST) Sender: Paolo Bonzini Message-ID: <5314799F.9010303@redhat.com> Date: Mon, 03 Mar 2014 13:46:23 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1393765632-2753-1-git-send-email-marcel.a@redhat.com> <1393765632-2753-4-git-send-email-marcel.a@redhat.com> <53145E21.3080803@redhat.com> <1393848455.11589.91.camel@localhost.localdomain> In-Reply-To: <1393848455.11589.91.camel@localhost.localdomain> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH RFC V2 3/9] hw/boards: converted current_machine to be an instance of QemuMachineCLass List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Marcel Apfelbaum Cc: peter.maydell@linaro.org, peter.crosthwaite@petalogix.com, ehabkost@redhat.com, mst@redhat.com, qemu-devel@nongnu.org, mtosatti@redhat.com, mdroth@linux.vnet.ibm.com, armbru@redhat.com, blauwirbel@gmail.com, quintela@redhat.com, agraf@suse.de, aliguori@amazon.com, edgar.iglesias@gmail.com, scottwood@freescale.com, imammedo@redhat.com, lcapitulino@redhat.com, afaerber@suse.de, rth@twiddle.net Il 03/03/2014 13:07, Marcel Apfelbaum ha scritto: >> > ... which brings us to what is missing here: you are not adding >> > current_machine as /machine in the QOM tree. :) > Is missing in purpose, I am not sure what are the consequences of changing the /machine > from container to an actual object. I am (almost) sure that this container has child > containers and I am looking for the rules: can an object act like a container? Yes, it can. "container" is a separate class than "object" only for documentation reasons. Paolo > So, I do intend of course to add it, once I have responded to the above issue.