qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: libvir-list@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [libvirt] [PATCH 4/7] qemu: Add monitor APIs to fetch CPUID data from QEMU
Date: Thu, 25 Jul 2013 15:13:35 +0100	[thread overview]
Message-ID: <20130725141334.GZ7382@redhat.com> (raw)
In-Reply-To: <51F1318E.5000801@suse.de>

On Thu, Jul 25, 2013 at 04:09:18PM +0200, Andreas Färber wrote:
> Am 25.07.2013 16:00, schrieb Eduardo Habkost:
> > libvirt
> > needs a way to find out how exactly "-machine foo-1.0 -cpu bar" looks
> > different from "-machine foo-1.1 -cpu bar",
> 
> Why? (What's the actual use case?)

It already takes a long time to just probe each QEMU binary, without
expanding that to probe each binary once for each machine type they
include. The idea of 'qemu -M none' was that we'd have a machine type
which did not do any hardware set, to query any aspect of the QEMU
binary capabilities.  If we have to also invoke qemu again with every
other machine type that is a failed design IMHO. It should not be beyond
the realm of possibility to make 'qemu -M none' provide information
about the CPU features for machines/cpus without needing to actually
creating instances of those machines.


Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2013-07-25 14:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1374595782.git.jdenemar@redhat.com>
     [not found] ` <dd23e4f4185196f173b78196cf47e4fe2dfc0057.1374595782.git.jdenemar@redhat.com>
     [not found]   ` <20130723161903.GL2477@redhat.com>
2013-07-23 16:27     ` [Qemu-devel] [libvirt] [PATCH 6/7] qemu: Probe QEMU binary for host CPU Eric Blake
2013-07-24 18:10     ` Eduardo Habkost
     [not found] ` <00920fe1cd728db02fa4c81602b359986a3cf2a1.1374595782.git.jdenemar@redhat.com>
     [not found]   ` <20130723163242.GQ2477@redhat.com>
     [not found]     ` <20130723172838.GJ4718@orkuz.home>
     [not found]       ` <20130723173246.GK4718@orkuz.home>
2013-07-24 18:25         ` [Qemu-devel] [libvirt] [PATCH 4/7] qemu: Add monitor APIs to fetch CPUID data from QEMU Eduardo Habkost
2013-07-25  9:14           ` Andreas Färber
2013-07-25 14:00             ` Eduardo Habkost
2013-07-25 14:09               ` Andreas Färber
2013-07-25 14:13                 ` Daniel P. Berrange [this message]
2013-07-25 18:02                 ` Eduardo Habkost
2013-07-26 12:31                   ` Andreas Färber
2013-07-26 13:51                     ` Eduardo Habkost
2013-07-25  9:45           ` Daniel P. Berrange
2013-07-25 13:15             ` Eduardo Habkost
2013-07-25 14:22               ` Daniel P. Berrange
     [not found]       ` <20130724100302.GK30336@redhat.com>
2013-07-24 18:31         ` Eduardo Habkost

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=20130725141334.GZ7382@redhat.com \
    --to=berrange@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=ehabkost@redhat.com \
    --cc=libvir-list@redhat.com \
    --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).