From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:56271) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RuoTH-00036R-W6 for qemu-devel@nongnu.org; Tue, 07 Feb 2012 12:04:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RuoTB-0007QN-R8 for qemu-devel@nongnu.org; Tue, 07 Feb 2012 12:04:47 -0500 Received: from mx1.redhat.com ([209.132.183.28]:25827) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RuoTB-0007Px-JU for qemu-devel@nongnu.org; Tue, 07 Feb 2012 12:04:41 -0500 Message-ID: <4F3159A1.5060700@redhat.com> Date: Tue, 07 Feb 2012 18:04:33 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <87ehu7pxvf.fsf@elfo.elfo> <4F312AFC.6020908@suse.de> <4F312C8A.9080700@redhat.com> <4F313BA8.9070601@codemonkey.ws> <4F31417F.2000102@redhat.com> <4F315033.7060105@codemonkey.ws> <4F3150F0.8060805@redhat.com> <4F315268.8030608@codemonkey.ws> In-Reply-To: <4F315268.8030608@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 7 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: quintela@redhat.com, Developers qemu-devel , KVM devel mailing list , =?ISO-8859-1?Q?Andreas?= =?ISO-8859-1?Q?_F=E4rber?= On 02/07/2012 05:33 PM, Anthony Liguori wrote: > Hrm, I don't like that very much. Yes, me neither actually. If the object representing the state of the OMAP board (struct omap_mpu_state_s) is QOMified, the clocks can easily get under it in the composition tree. Right now, that part is not even qdev. :) > OMAP clocks are devices. Don't they belong in the devices hierarchy > under the omap-clocks branch? If they were devices, yes. But they're not, and it wouldn't have been a great time investment to refactor them. :) Perhaps we can have /machine instead of /devices, a more generic name would do well. Then... > The fact that they aren't DeviceState's is because DeviceState is a pile > of cruft. Perhaps we should introduce a more streamlined Device base > class and rename DeviceState to LegacyDevice or something like that. ... light-weight components can inherit straight from Object and go under /machine. There would be /machine/clocks for example. Paolo