From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:45031) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S1T1A-0003bx-KZ for qemu-devel@nongnu.org; Sat, 25 Feb 2012 20:35:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S1T0x-00055Y-Vq for qemu-devel@nongnu.org; Sat, 25 Feb 2012 20:35:16 -0500 Received: from mail-pw0-f45.google.com ([209.85.160.45]:64754) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S1T0x-000558-QL for qemu-devel@nongnu.org; Sat, 25 Feb 2012 20:35:03 -0500 Received: by pbbro12 with SMTP id ro12so4890065pbb.4 for ; Sat, 25 Feb 2012 17:35:02 -0800 (PST) Message-ID: <4F498C43.1070803@codemonkey.ws> Date: Sat, 25 Feb 2012 19:34:59 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <1330198969-27364-1-git-send-email-aliguori@us.ibm.com> <1330198969-27364-8-git-send-email-aliguori@us.ibm.com> <4F494F91.1000509@codemonkey.ws> <4F498B63.3030202@suse.de> In-Reply-To: <4F498B63.3030202@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH 07/10] qtest: IRQ interception infrastructure (v2) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?ISO-8859-1?Q?Andreas_F=E4rber?= Cc: Paolo Bonzini , qemu-devel@nongnu.org, Jan Kiszka On 02/25/2012 07:31 PM, Andreas Färber wrote: > Am 25.02.2012 22:16, schrieb Anthony Liguori: >> On 02/25/2012 02:20 PM, Paolo Bonzini wrote: >>> On 02/25/2012 08:42 PM, Anthony Liguori wrote: >>>> + >>>> object_property_add_child(object_resolve_path("/i440fx/piix3", NULL), >>>> + "ioapic", OBJECT(dev), NULL); >>> >>> Jan objected to putting this under /i440fx/piix3. >> >> I think for our model, having it as a child property makes quite a lot >> of sense. > > Weren't you discussing rearranging the tree so that devices are under a > separate node from block devices etc. (e.g., /devices)? Would be a good > idea to introduce a (dummy) object_resolve_device_path() to avoid having > to change hardcoded absolute string paths like the above later. No need. object_resolve_path("i440fx/piix3", NULL) would have the same effect. But I also don't think it's necessary. Direct calls to object_resolve_path almost always indicates the need to refactor code. Regards, Anthony Liguori > Or do that change first so that new paths like this one at least don't > need to be touched again. > > Andreas >