From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34993) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WJOyw-0008OS-SF for qemu-devel@nongnu.org; Fri, 28 Feb 2014 10:04:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WJOyp-0007Y9-Dr for qemu-devel@nongnu.org; Fri, 28 Feb 2014 10:04:10 -0500 Received: from mail-pa0-f52.google.com ([209.85.220.52]:52243) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WJOyp-0007VP-8F for qemu-devel@nongnu.org; Fri, 28 Feb 2014 10:04:03 -0500 Received: by mail-pa0-f52.google.com with SMTP id fb1so864926pad.39 for ; Fri, 28 Feb 2014 07:04:01 -0800 (PST) Message-ID: <5310A55B.7030602@ozlabs.ru> Date: Sat, 01 Mar 2014 02:03:55 +1100 From: Alexey Kardashevskiy MIME-Version: 1.0 References: <1392904246-15575-1-git-send-email-aik@ozlabs.ru> <1392904246-15575-4-git-send-email-aik@ozlabs.ru> <530609F9.1060105@redhat.com> <530F14C2.2050808@suse.de> <530F1670.2070701@redhat.com> <1393511950.31381.34.camel@localhost.localdomain> <530F52C5.3080209@redhat.com> <1393513484.31381.36.camel@localhost.localdomain> In-Reply-To: <1393513484.31381.36.camel@localhost.localdomain> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v5 3/6] vl: allow customizing the class of /machine List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Marcel Apfelbaum , Paolo Bonzini Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, Alexander Graf , =?UTF-8?B?QW5kcmU=?= =?UTF-8?B?YXMgRsOkcmJlcg==?= On 02/28/2014 02:04 AM, Marcel Apfelbaum wrote: > On Thu, 2014-02-27 at 15:59 +0100, Paolo Bonzini wrote: >> Il 27/02/2014 15:39, Marcel Apfelbaum ha scritto: >>>>> >>>>> Each of them highlights one of the two aspects that, in my opinion, make >>>>> QOM interesting (respectively, unification of interfaces and the >>>>> containment tree). >>> I was planning to tackle the replacement of the machine from a container >>> to an actual object too, however this patch conflicts with my >>> series because I already have a QOM Machine object created *always* >>> and this patch adds another object *sometimes*. >>> >>> Is this patch's functionality in use yet? Any idea how to merge those ideas? >> >> pseries simply wants to make /machine implement the FWPathProvider >> interface. As long as you have a way for boards to specify a TypeInfo >> for /machine, this patch will not get in the way. > Thanks Paolo! I'll be aware not to brake this functionality. > Marcel What is the outcome of this discussion for the patches I posted? Do I have to wait till you finish that machine properties rework and repost or...? Thanks. -- Alexey