From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Pavel Dovgalyuk" <dovgaluk@ispras.ru>
Cc: mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
"'Фурсова Наталия'" <Natalia.Fursova@ispras.ru>,
armbru@redhat.com
Subject: Re: [Qemu-devel] Querying possible -cpu variants
Date: Fri, 25 Jan 2019 07:31:35 -0600 [thread overview]
Message-ID: <c01e8238-5da8-aaf5-8ab2-1484f8cd0871@redhat.com> (raw)
In-Reply-To: <20190125101032.GA4498@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
On 1/25/19 4:10 AM, Daniel P. Berrangé wrote:
>
>> 2. Add QMP command for requesting this list.
>
> This already exists as the 'query-cpu-definitions' command
What's more, you can use libvirt code as an example of how to parse QMP
commands to see what features are present. And if the existing QMP
commands don't answer a question you need answered, enhancing QMP is a
worthwhile patch (other projects, like libvirt, will probably also end
up using those enhancements). Among other things, we know that our
command-line parameters are not yet fully queryable by QMP.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-01-25 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 9:58 [Qemu-devel] Querying possible -cpu variants Pavel Dovgalyuk
2019-01-25 10:04 ` Peter Maydell
2019-01-25 10:10 ` Daniel P. Berrangé
2019-01-25 10:38 ` Pavel Dovgalyuk
2019-01-25 13:31 ` Eric Blake [this message]
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=c01e8238-5da8-aaf5-8ab2-1484f8cd0871@redhat.com \
--to=eblake@redhat.com \
--cc=Natalia.Fursova@ispras.ru \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dovgaluk@ispras.ru \
--cc=mdroth@linux.vnet.ibm.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).