From: "Natalia Fursova" <Natalia.Fursova@ispras.ru>
To: "'Paolo Bonzini'" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, 'Паша' <Pavel.Dovgaluk@ispras.ru>
Subject: Re: [Qemu-devel] qgraph
Date: Wed, 5 Jun 2019 17:22:30 +0300 [thread overview]
Message-ID: <001e01d51baa$1c190650$544b12f0$@Fursova@ispras.ru> (raw)
In-Reply-To: <ec5033a4-5c68-91b7-ca9e-a1f38c990221@redhat.com>
I see.
We need this opportunity and want to implement it. Will it ok for QOM
conception?
Best regards,
Natalia
-----Original Message-----
From: Paolo Bonzini [mailto:pbonzini@redhat.com]
Sent: Wednesday, June 05, 2019 4:07 PM
To: Natalia Fursova; qemu-devel@nongnu.org; 'Паша'
Subject: Re: [Qemu-devel] qgraph
On 05/06/19 14:34, Natalia Fursova wrote:
>
> Thank you for your answer. I would like to clarify something about the qmp
> commands.
> For example, consider SCSI controller "lsi53c895a". For getting
information
> we use two commands: "device-list-properties" and "qom-list-properties".
> Output consists of many properties, but there is no information about
> provided buses by this device. Is there a qmp command which provides this
> information?
Unfortunately there is no information in QMP about buses that are
provided. qom-list-types gives the buses that are requested.
Paolo
next prev parent reply other threads:[~2019-06-05 14:23 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 ` [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 [this message]
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='001e01d51baa$1c190650$544b12f0$@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).