From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53797) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UtKl0-0001dd-S0 for qemu-devel@nongnu.org; Sun, 30 Jun 2013 12:45:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UtKky-0007Kv-MZ for qemu-devel@nongnu.org; Sun, 30 Jun 2013 12:45:46 -0400 Received: from cantor2.suse.de ([195.135.220.15]:53551 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UtKky-0007Kk-92 for qemu-devel@nongnu.org; Sun, 30 Jun 2013 12:45:44 -0400 Message-ID: <51D060B1.3080904@suse.de> Date: Sun, 30 Jun 2013 18:45:37 +0200 From: =?ISO-8859-15?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 00/26] use realizefn for SysBusDevice, part 1 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Hu Tao Cc: Peter Maydell , Peter Crosthwaite , Eduardo Habkost , qemu-devel , Anthony Liguori , Paolo Bonzini , Igor Mammedov Hi, Am 22.06.2013 10:50, schrieb Hu Tao: > This series updates part of devices inheriting from SysbusDevice > to use DeviceState::realize, and QOM'ify them. >=20 > These devices are default to x86_64-softmmu. I'm planning to > make patches in the same manner, that is, each series is for > devices default to each target. After all devices are converted > to realizefn, SysBusDevice::init can be removed. This series looks promising. As was requested by others, please rebase (possibly on qom-next if there's conflicts with Peter M.'s patch?) and reorder the patches so that QOM cast macros come before more functional changes (the former can be picked up more quickly). For ARM I am looking into a few devices surrounding cpu/a9mpcore.c. Paolo has announced a PULL for his MemoryRegion refactorings for beginning of the week, which is likely to conflict with realizefn work. As a reminder for realize series (we should definitely document this!): * QOM realize functions should not create new devices as that creates problems with recursive realized =3D true and will prohibit changing static device properties through QMP. (Therefore more review work.) * Care must be taken with bus creation since qbus_create[_inplace]() / qbus_realize() check for DeviceState::id, which is still NULL at instance_init time. (OHCI looked good for instance.) Regards, Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg