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: Or Goshen <oberonc@gmail.com>,
	qemu-devel@nongnu.org, Or Goshen <or@heartbeat.com>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Add a command to QMP to list the supported devices
Date: Mon, 24 Feb 2014 14:44:09 +0100	[thread overview]
Message-ID: <530B4CA9.8030508@redhat.com> (raw)
In-Reply-To: <530B4BD4.7030808@suse.de>

Il 24/02/2014 14:40, Andreas Färber ha scritto:
> Am 24.02.2014 10:31, schrieb Paolo Bonzini:
>> Il 24/02/2014 10:23, Or Goshen ha scritto:
>>> From: Or Goshen <or@heartbeat.com>
>>>
>>> Was done on behalf of Intel Corp.
>>
>> Hi Or,
>>
>> you can use qom-list-types for this purpose.
>
> That can return a list of types, but there is no way to access the
> DeviceClass-specific bus, alias, desc values, is there?

The bus value can be retrieved indirectly from the class hierarchy. 
Aliases are deprecated.

Desc could be moved to the object class and added to qom-list-types.

> It sounds to me as if they are trying to recreate the -device ? output
> in machine-readable form.

Indeed.  The question is why they need "-device ?".  If it is just for 
"is the device supported" (as was the case for libvirt before it started 
using qom-list-types), then a new command is unnecessary.

Paolo

  reply	other threads:[~2014-02-24 13:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24  9:23 [Qemu-devel] [PATCH] Add a command to QMP to list the supported devices Or Goshen
2014-02-24  9:31 ` Paolo Bonzini
2014-02-24 13:40   ` Andreas Färber
2014-02-24 13:44     ` Paolo Bonzini [this message]
2014-02-24 13:49     ` Or Goshen
2014-02-24 18:05       ` Paolo Bonzini
2014-02-24 15:40 ` Eric Blake

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=530B4CA9.8030508@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=lcapitulino@redhat.com \
    --cc=oberonc@gmail.com \
    --cc=or@heartbeat.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).