qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: 'Паша' <Pavel.Dovgaluk@ispras.ru>,
	qemu-devel@nongnu.org,
	"Natalia Fursova" <Natalia.Fursova@ispras.ru>,
	armbru@redhat.com
Subject: Re: [Qemu-devel] qgraph
Date: Mon, 10 Jun 2019 18:18:31 +0200	[thread overview]
Message-ID: <c49abf01-c209-b206-edee-507c31269011@redhat.com> (raw)
In-Reply-To: <79b821a4-7cc0-2461-7ca4-d71c3e5ee4ef@suse.de>

On 10/06/19 18:12, Andreas Färber wrote:
> Am 10.06.19 um 15:52 schrieb Paolo Bonzini:
>> On 10/06/19 15:28, Andreas Färber wrote:
>>> So if we want a new QMP operation, the most sense would probably make
>>> where-can-I-attach-type(foo) returning a list of QOM paths, showing only
>>> the first free slot per bus. That would allow a more efficient lookup
>>> implementation inside QEMU than needing to check each slot[n] property
>>> via qom-get after discovering it with qom-list.
>>
>> Note that what Natalia is seeking is an introspection mechanism to be
>> used _before_ creating a virtual machine though.
> 
> QMP implied creating a virtual machine though.

Yes, but you can start QEMU with -M none and just invoke QOM
introspection commands.

> This then goes back to the long-discussed topic of not doing recursive
> realized=true when starting halted with -s but deferring that to the
> cont operation. I doubt that's been implemented in the meantime?

Nope.

Paolo


  reply	other threads:[~2019-06-10 16:20 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
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 [this message]
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=c49abf01-c209-b206-edee-507c31269011@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Natalia.Fursova@ispras.ru \
    --cc=Pavel.Dovgaluk@ispras.ru \
    --cc=afaerber@suse.de \
    --cc=armbru@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).