From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D610AC43218 for ; Tue, 11 Jun 2019 13:54:52 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id AB7EB206BB for ; Tue, 11 Jun 2019 13:54:52 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AB7EB206BB Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:59234 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hahEh-0000WX-V1 for qemu-devel@archiver.kernel.org; Tue, 11 Jun 2019 09:54:51 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59395) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hahBz-0006Ny-HZ for qemu-devel@nongnu.org; Tue, 11 Jun 2019 09:52:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hahBy-0005de-DE for qemu-devel@nongnu.org; Tue, 11 Jun 2019 09:52:03 -0400 Received: from mx2.suse.de ([195.135.220.15]:50838 helo=mx1.suse.de) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hahBy-0005cw-6B for qemu-devel@nongnu.org; Tue, 11 Jun 2019 09:52:02 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id C4655AE24; Tue, 11 Jun 2019 13:51:59 +0000 (UTC) To: Paolo Bonzini , Markus Armbruster References: <5cf62de9.1c69fb81.66fc.8f4fSMTPIN_ADDED_BROKEN@mx.google.com> <1e9e4edd-f4ad-d8d6-95a2-e0aeab89510d@redhat.com> <5cf7b6e6.1c69fb81.1cdca.e260SMTPIN_ADDED_BROKEN@mx.google.com> <003b01d51f72$5e6f4160$1b4dc420$@Fursova@ispras.ru> <67806828-f666-0c9c-00fc-b520f15013d9@suse.de> <98826c5f-4a74-5364-2aef-28a10db12c20@suse.de> <39250506-f38f-c440-5728-7b970d32ab41@redhat.com> <79b821a4-7cc0-2461-7ca4-d71c3e5ee4ef@suse.de> <87o934sdot.fsf@dusky.pond.sub.org> <8d391b41-bf6d-b83b-7b22-25fefa18c518@redhat.com> From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Openpgp: preference=signencrypt Organization: SUSE Linux GmbH Message-ID: <8484a155-0721-a09a-df67-5d85cb22b14c@suse.de> Date: Tue, 11 Jun 2019 15:51:59 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <8d391b41-bf6d-b83b-7b22-25fefa18c518@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic] X-Received-From: 195.135.220.15 Subject: Re: [Qemu-devel] qgraph X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Natalia Fursova , qemu-devel@nongnu.org, =?UTF-8?B?J9Cf0LDRiNCwJw==?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" Am 11.06.19 um 12:31 schrieb Paolo Bonzini: > On 11/06/19 10:56, Markus Armbruster wrote: >> Yes, this is how introspection (both QMP and QOM) is commonly used. >> Just keep in mind one difference: QMP is static, QOM is dynamic. >> >> QMP being static means it's defined at compile time. So is the value = of >> query-qmp-schema. Same QEMU build, same value. This permits caching. >> >> QOM being dynamic means to introspect an object's properties, you have >> to create it. Worse, an object's properties may (in theory) change at >> any time. *Properties*, not just property *values*. In practice, I'd >> expect properties to change only at realize time. >=20 > Right, and we should move more towards class-based properties so that > the dynamic nature of QOM is only used for the bare minimum needed (e.g= . > memory regions). I believe it was Paolo who once reminded me that all child<> properties are dynamic. And link<> properties for bus devices are also dynamic. I don't see a good way around that. Regards, Andreas --=20 SUSE Linux GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany GF: Felix Imend=C3=B6rffer, Mary Higgins, Sri Rasiah HRB 21284 (AG N=C3=BCrnberg)