From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 7 Date: Tue, 07 Feb 2012 12:01:16 -0600 Message-ID: <4F3166EC.7000002@codemonkey.ws> References: <87ehu7pxvf.fsf@elfo.elfo> <4F312AFC.6020908@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: quintela@redhat.com, Developers qemu-devel , KVM devel mailing list To: =?ISO-8859-15?Q?Andreas_F=E4rber?= Return-path: Received: from mail-pw0-f46.google.com ([209.85.160.46]:48956 "EHLO mail-pw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752276Ab2BGSBV (ORCPT ); Tue, 7 Feb 2012 13:01:21 -0500 Received: by pbcun15 with SMTP id un15so30129pbc.19 for ; Tue, 07 Feb 2012 10:01:21 -0800 (PST) In-Reply-To: <4F312AFC.6020908@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: On 02/07/2012 07:45 AM, Andreas F=E4rber wrote: > Am 06.02.2012 20:25, schrieb Juan Quintela: >> Please send in any agenda items you are interested in covering. > > I had some follow-up questions to the last call that remained > unanswered. We don't really need a call for that though, email is fin= e. > > http://lists.gnu.org/archive/html/qemu-devel/2012-01/msg04065.html > > How is the realize step (DeviceState::init) supposed to translate to > Object-derived classes (e.g., CPU) and where to draw the line between > initfn and realize. Realize probably should be folded into Object or some intermediate obje= ct. The idea is that there will be a realized boolean property. When the l= evel=20 changes, it will invoke a realize() or unrealize() method depending on = the=20 direction. DeviceState will implement realize() and invoke init(). Fo= r=20 unrealize(), it will invoke exit(). > For virtual methods Anthony outlined the intended scheme here: > http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg00622.html > (Derived classes should save the parent's function pointer in their o= wn > Class and initialize it from the parent class' function pointer.) > > Another topic that can be answered by email is what the time planning > for the 4th QOM series looks like. Are there things that developers o= f > new devices should keep in mind / start doing differently wrt SysBus? I think I answered this elsewhere. Regards, ANthony Liguori > Andreas >