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.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MSGID_MULTIPLE_AT,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no 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 02C2FC4646D for ; Tue, 2 Jul 2019 11:51:02 +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 D385421721 for ; Tue, 2 Jul 2019 11:51:01 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D385421721 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=ispras.ru Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:51940 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hiHJM-0008Pm-EV for qemu-devel@archiver.kernel.org; Tue, 02 Jul 2019 07:51:00 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:34306) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hiHCk-0004BU-GM for qemu-devel@nongnu.org; Tue, 02 Jul 2019 07:44:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hiHCi-0006Ml-Hc for qemu-devel@nongnu.org; Tue, 02 Jul 2019 07:44:10 -0400 Received: from mail.ispras.ru ([83.149.199.45]:44348) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hiHCg-0006Gc-PJ for qemu-devel@nongnu.org; Tue, 02 Jul 2019 07:44:08 -0400 Received: from NATALIAFURSOVA (unknown [85.142.117.226]) by mail.ispras.ru (Postfix) with ESMTPSA id B195C540081; Tue, 2 Jul 2019 14:44:02 +0300 (MSK) From: "Natalia Fursova" 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> <87ftogp7f5.fsf@dusky.pond.sub.org> <4ed45e59-6d7d-a9ea-9af3-7ec336c7ec3d@redhat.com> In-Reply-To: <4ed45e59-6d7d-a9ea-9af3-7ec336c7ec3d@redhat.com> Date: Tue, 2 Jul 2019 14:44:05 +0300 Message-ID: <014c01d530cb$73ff1950$5bfd4bf0$@Fursova@ispras.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdUgW9l5XmsGj7jwR1SPV3cjsX4VzQQbuK7w Content-Language: ru X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 83.149.199.45 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: =?utf-8?Q?'Andreas_F=C3=A4rber'?= , =?utf-8?B?J9Cf0LDRiNCwJw==?= , qemu-devel@nongnu.org Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" Hi there again! Thank you for your answers, I have new question. =20 I want to identify PCI devices (e.g. network cards) and observed one = strange thing. I use qmp command "qom-list-type" and build tree from it = output. Some items don't have parent and don't give information about = themselves. E. g. "e1000-base". It has three children and it belongs to = PCI devices, but I can't know it, cuz command "qom-list-properties" = returns empty message. There is no information about "e1000-base" in "qom-list-type" output. It = is referenced only as a parent for network cards. Is it ok? Maybe is there other way for get information about all PCI = devices? Best regards, Natalia -----Original Message----- From: Paolo Bonzini [mailto:pbonzini@redhat.com]=20 Sent: Tuesday, June 11, 2019 4:45 PM To: Markus Armbruster Cc: Natalia Fursova; Andreas F=C3=A4rber; '=D0=9F=D0=B0=D1=88=D0=B0'; = qemu-devel@nongnu.org Subject: Re: [Qemu-devel] qgraph On 11/06/19 15:39, Markus Armbruster wrote: >> 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). > What are we doing to make new code conform to that? >=20 > What are we doing to update existing code? Almost nothing and completely nothing. :( Paolo