qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>,
	Jiri Denemark <jdenemar@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	David Hildenbrand <david@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] i386: Support "-cpu host" on TCG too
Date: Thu, 19 Jan 2017 17:50:03 +0000	[thread overview]
Message-ID: <20170119175003.GJ16641@redhat.com> (raw)
In-Reply-To: <20170116195452.23532-1-ehabkost@redhat.com>

On Mon, Jan 16, 2017 at 05:54:52PM -0200, Eduardo Habkost wrote:
> Change the meaning of "-cpu host" to "enable all features
> supported by the accelerator in the current host", so that it can
> be used to enable/query all features supported by TCG.
> 
> To make sure "host" is still at the end of the list in "-cpu
> help", add a "ordering" field that will be used when sorting the
> CPU model list.

To be clear, "-cpu host" for TCG is not talking about the actual
host OS feature support, right ? x86_64 TCG can be run on a ppc host,
so presumably "-cpu host" just means "all features that this TCG binary
is able to emulate" ?

This feels like it is introducing scope for confusion vs KVM -cpu host,
so I wonder if different naming is better for this.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|

  parent reply	other threads:[~2017-01-19 17:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 19:54 [Qemu-devel] [PATCH] i386: Support "-cpu host" on TCG too Eduardo Habkost
2017-01-17 13:39 ` Richard W.M. Jones
2017-01-17 14:03   ` Eduardo Habkost
2017-01-17 13:42 ` Richard W.M. Jones
2017-01-17 13:44   ` Richard W.M. Jones
2017-01-17 13:57     ` Richard W.M. Jones
2017-01-17 14:05       ` Eduardo Habkost
2017-01-17 14:19         ` Richard W.M. Jones
2017-01-17 17:43 ` David Hildenbrand
2017-01-19 14:52   ` Cornelia Huck
2017-02-16 14:43   ` Christian Borntraeger
2017-02-16 14:44     ` Christian Borntraeger
2017-01-19 17:50 ` Daniel P. Berrange [this message]
2017-01-19 18:22   ` Peter Maydell
2017-01-19 18:31     ` Eduardo Habkost
2017-01-19 18:38       ` Daniel P. Berrange
2017-01-19 19:02         ` 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=20170119175003.GJ16641@redhat.com \
    --to=berrange@redhat.com \
    --cc=david@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jdenemar@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).