From: Eric Blake <eblake@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Cc: "Peter Krempa" <pkrempa@redhat.com>,
libvir-list@redhat.com, qemu-devel@nongnu.org,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Jiri Denemark" <jdenemar@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [libvirt] [RFC 0/5] Allow object-add on X86CPU subclasses, for CPU model probing
Date: Tue, 06 May 2014 16:13:37 -0600 [thread overview]
Message-ID: <53695E91.1020305@redhat.com> (raw)
In-Reply-To: <20140506201957.GW3363@otherpad.lan.raisama.net>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
On 05/06/2014 02:19 PM, Eduardo Habkost wrote:
>> IMHO, libvirt side should take advantage of information QEMU already
>> provides.
>>
>
> Current API requires re-running QEMU to query the information. This
> series allows it to be run with the "-machine none" QEMU instance that
> is already run by libvirt.
Therein is the reason libvirt isn't using what qemu already has -
spawning multiple qemu instances (one per reported machine type)
multiplied by the number of qemu binaries does not scale well, when
compared to starting a single qemu -machine none, and doing all queries
on that one machine. So the point of this patch is getting us closer to
the point where libvirt can learn accurate cpu model information for
multiple machines all from a single qemu invocation.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-05-06 22:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398889773-14652-1-git-send-email-ehabkost@redhat.com>
2014-05-02 13:45 ` [Qemu-devel] [RFC 0/5] Allow object-add on X86CPU subclasses, for CPU model probing Igor Mammedov
2014-05-02 14:43 ` Eduardo Habkost
2014-05-02 14:54 ` Paolo Bonzini
2014-05-02 16:43 ` Eduardo Habkost
2014-05-06 7:22 ` Igor Mammedov
2014-05-06 14:42 ` Eduardo Habkost
2014-05-06 20:01 ` Igor Mammedov
2014-05-06 20:19 ` Eduardo Habkost
2014-05-06 20:29 ` Andreas Färber
2014-05-08 18:29 ` Eduardo Habkost
2014-05-15 12:35 ` Igor Mammedov
2014-05-15 13:07 ` Eduardo Habkost
2014-05-15 13:09 ` Andreas Färber
2014-05-15 13:48 ` Igor Mammedov
2014-05-15 14:03 ` Eduardo Habkost
2014-05-16 14:52 ` Igor Mammedov
2014-05-16 15:16 ` Eduardo Habkost
2014-05-16 14:57 ` Andreas Färber
2014-05-06 22:13 ` Eric Blake [this message]
2014-05-15 12:14 ` Igor Mammedov
2014-05-15 13:35 ` Eduardo Habkost
[not found] ` <1398889773-14652-2-git-send-email-ehabkost@redhat.com>
2014-05-15 12:28 ` [Qemu-devel] [RFC 1/5] cpu: Initialize cpu->stopped=true earlier Igor Mammedov
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=53695E91.1020305@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=jdenemar@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pkrempa@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).