qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Pavel Dovgalyuk <dovgaluk@ispras.ru>
Cc: qemu-devel@nongnu.org, armbru@redhat.com,
	"'Фурсова Наталия'" <Natalia.Fursova@ispras.ru>,
	mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] Querying possible -cpu variants
Date: Fri, 25 Jan 2019 10:10:32 +0000	[thread overview]
Message-ID: <20190125101032.GA4498@redhat.com> (raw)
In-Reply-To: <003301d4b494$775585c0$66009140$@ru>

On Fri, Jan 25, 2019 at 12:58:04PM +0300, Pavel Dovgalyuk wrote:
> Hello.
> 
>  
> 
> We are making GUI for QEMU (which also should allow convenient record/replay command line
> generation): https://github.com/ispras/qemu-gui
> 
>  
> 
> To fill the combo box in CPU selection form we run QEMU with "-cpu help" command and parse its
> output.
> 
> The format of this list depends on target. Therefore our parsing code does not look good (and also
> may corrupt someday).
> 
>  
> 
> Is there a better way of requesting this information?
> 
>  
> 
> Or we should do one of the following:
> 
> 1.       Patch all targets and make the uniform "-cpu help" output format

Machine parsing of "help" output is not supported by the QEMU project.
This must all be done via the QMP interfaces.

> 2.       Add QMP command for requesting this list.

This already exists as the 'query-cpu-definitions' command


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  parent reply	other threads:[~2019-01-25 10:10 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é [this message]
2019-01-25 10:38   ` Pavel Dovgalyuk
2019-01-25 13:31   ` 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=20190125101032.GA4498@redhat.com \
    --to=berrange@redhat.com \
    --cc=Natalia.Fursova@ispras.ru \
    --cc=armbru@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).