From: "Natalia Fursova" <Natalia.Fursova@ispras.ru>
To: qemu-devel@nongnu.org, pbonzini@redhat.com,
Паша <Pavel.Dovgaluk@ispras.ru>
Subject: Re: [Qemu-devel] qgraph
Date: Tue, 4 Jun 2019 11:37:37 +0300 [thread overview]
Message-ID: <000301d51ab0$c3f1aee0$4bd50ca0$@Fursova@ispras.ru> (raw)
In-Reply-To:
ping
Best regards,
Natalia
From: Наталья Фурсова [mailto:Natalia.Fursova@ispras.ru]
Sent: Wednesday, May 29, 2019 2:57 PM
To: 'qemu-devel@nongnu.org'; 'pbonzini@redhat.com'; Паша
(Pavel.Dovgaluk@ispras.ru)
Subject: qgraph
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.
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 reply other threads:[~2019-06-04 8:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 8:37 Natalia Fursova [this message]
[not found] <5cf62de9.1c69fb81.66fc.8f4fSMTPIN_ADDED_BROKEN@mx.google.com>
2019-06-04 15:06 ` [Qemu-devel] qgraph Paolo Bonzini
2019-06-05 12:34 ` 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
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='000301d51ab0$c3f1aee0$4bd50ca0$@Fursova@ispras.ru' \
--to=natalia.fursova@ispras.ru \
--cc=Pavel.Dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--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).