From: Paolo Bonzini <pbonzini@redhat.com>
To: "Natalia Fursova" <Natalia.Fursova@ispras.ru>,
qemu-devel@nongnu.org, Паша <Pavel.Dovgaluk@ispras.ru>
Subject: Re: [Qemu-devel] qgraph
Date: Tue, 4 Jun 2019 17:06:20 +0200 [thread overview]
Message-ID: <1e9e4edd-f4ad-d8d6-95a2-e0aeab89510d@redhat.com> (raw)
In-Reply-To: <5cf62de9.1c69fb81.66fc.8f4fSMTPIN_ADDED_BROKEN@mx.google.com>
On 04/06/19 10:37, Natalia Fursova wrote:
> Hello, Paolo!
>
> We develop GUI for Qemu and want to implement graphical interface for
> configuring the device tree. To do this we need to detect list of the
> devices supported by any specific platform.
>
> Then we use this tree for command line generation.
>
> Existing qmp commands don't supply enough information to build the tree.
> They miss bus and interface data.
Hi!
Bus data is implicit in the parent class provided by QMP. For example,
pci-device is the superclass of PCI devices, scsi-device is the
superclass of SCSI devices, etc.
qgraph is indeed similar, but it is only used by test cases, not by QEMU
itself. The difference is that qgraph links together _drivers_ for the
devices, and so it is limited to those devices that have tests. For
some ideas behind qgraph, see
https://wiki.qemu.org/Features/qtest_driver_framework.
Paolo
>
>
>
> There is something called 'qgraph' in Qemu. It looks similar to data
> structures in our GUI tool.
>
>
>
> Tell me please, do you have a plan on improving this interface? We found the
> following hardcoded lines in the tests:
>
> qos_node_consumes("megasas", "pci-bus", &opts);
>
> qos_node_produces("megasas", "pci-device");
>
>
>
> And we wanted to extend QMP to query this kind of information.
>
>
>
>
>
> Best regards,
>
> Natalia
>
>
>
next parent reply other threads:[~2019-06-04 15:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5cf62de9.1c69fb81.66fc.8f4fSMTPIN_ADDED_BROKEN@mx.google.com>
2019-06-04 15:06 ` Paolo Bonzini [this message]
2019-06-05 12:34 ` [Qemu-devel] qgraph Natalia Fursova
[not found] ` <5cf7b6e6.1c69fb81.1cdca.e260SMTPIN_ADDED_BROKEN@mx.google.com>
2019-06-05 13:07 ` Paolo Bonzini
2019-06-05 14:22 ` Natalia Fursova
2019-06-10 9:53 ` Natalia Fursova
2019-06-10 11:57 ` Andreas Färber
2019-06-10 12:03 ` Paolo Bonzini
2019-06-10 13:28 ` Andreas Färber
2019-06-10 13:52 ` Paolo Bonzini
2019-06-10 16:12 ` Andreas Färber
2019-06-10 16:18 ` Paolo Bonzini
2019-06-11 8:56 ` Markus Armbruster
2019-06-11 10:31 ` Paolo Bonzini
2019-06-11 13:39 ` Markus Armbruster
2019-06-11 13:44 ` Paolo Bonzini
2019-07-02 11:44 ` Natalia Fursova
2019-07-02 15:26 ` Markus Armbruster
2019-07-03 8:19 ` Natalia Fursova
[not found] ` <5d1b4524.1c69fb81.ddba5.77bdSMTPIN_ADDED_BROKEN@mx.google.com>
2019-07-02 11:54 ` Peter Maydell
2019-06-11 13:51 ` Andreas Färber
2019-06-04 8:37 Natalia Fursova
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1e9e4edd-f4ad-d8d6-95a2-e0aeab89510d@redhat.com \
--to=pbonzini@redhat.com \
--cc=Natalia.Fursova@ispras.ru \
--cc=Pavel.Dovgaluk@ispras.ru \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).