qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Aurelien Jarno" <aurelien@aurel32.net>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2 0/6] target-i386: Make most CPU models work with "enforce" out of the box
Date: Wed, 27 Aug 2014 16:33:54 +0200	[thread overview]
Message-ID: <53FDEC52.5040909@redhat.com> (raw)
In-Reply-To: <20140827140535.GG32084@thinpad.lan.raisama.net>

Il 27/08/2014 16:05, Eduardo Habkost ha scritto:
> On Wed, Aug 27, 2014 at 03:36:51PM +0200, Paolo Bonzini wrote:
>> Il 26/08/2014 20:01, Eduardo Habkost ha scritto:
>>> So maybe that's good news, as things can be simpler if we make both TCG
>>> and KVM have similar behavior:
>>>
>>> * qemu64: a conservative default that should work out of the box on
>>>   most systems, for both TCG and KVM. That's already the current status,
>>>   we just need to document it.
>>>
>>> * -cpu host: for people who want every possible feature to be enabled
>>>   (but without cross-version live-migration support). We can easily add
>>>   support for "-cpu host" to TCG, too.
>>
>> This means that "-cpu host" has different meanings in KVM and TCG.  Is
>> that an advantage or a disadvantage?
> 
> It is the same meaning to me: "enable everything that's possible,
> considering what's provided by the underlying accelerator". The "host"
> name is misleading, though, because on KVM it is close to the host CPU,
> but on TCG it depends solely on TCG's capabilities.

True.  It's not very intuitive, but it is the same concept for processor
capabilities.

Though for some leaves that do not correspond to processor capabilities,
"-cpu host" does set them to the host values.  This is not just the
cache model, but also the family/model/stepping/vendor.

For the TCG case, when running on a Nehalem it would be weird to see a
Nehalem guest with SMAP or ADOX support...  I'm not sure it would even
work to have SVM with an Intel vendor. :)

>> If I have to choose blindly, I'd rather give different (but sane)
>> meanings to "-cpu qemu64" and the same meanings to "-cpu host"...
>> Basically "-cpu qemu32/64" on KVM would be changed automatically to
>> kvm32/64.
> 
> This (different meanings to qemu64) is what I was proposing first,

Good.

> except for the "same meaning to -cpu host" part. What exactly would you
> expect "-cpu host" to mean on TCG?

Emulate (as much as possible of) a SandyBridge if I'm running on a
SandyBridge, etc.

"-cpu qemu64" would be the best CPU that TCG can do, with a standard
family/model/stepping/vendor slapped on top.

Paolo

  reply	other threads:[~2014-08-27 14:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25 20:45 [Qemu-devel] [PATCH v2 0/6] target-i386: Make most CPU models work with "enforce" out of the box Eduardo Habkost
2014-08-25 20:45 ` [Qemu-devel] [PATCH v2 1/6] pc: Create pc_compat_2_1() functions Eduardo Habkost
2014-08-25 20:45 ` [Qemu-devel] [PATCH v2 2/6] target-i386: Rename KVM auto-feature-enable compat function Eduardo Habkost
2014-08-25 20:45 ` [Qemu-devel] [PATCH v2 3/6] target-i386: Disable CPUID_ACPI by default on KVM mode Eduardo Habkost
2014-08-25 20:45 ` [Qemu-devel] [PATCH v2 4/6] target-i386: Remove unsupported bits from all CPU models Eduardo Habkost
2014-08-25 20:45 ` [Qemu-devel] [PATCH v2 5/6] target-i386: Don't enable nested VMX by default Eduardo Habkost
2014-08-25 20:45 ` [Qemu-devel] [PATCH v2 6/6] target-i386: Disable SVM by default in KVM mode Eduardo Habkost
2014-08-26 12:56 ` [Qemu-devel] [PATCH v2 0/6] target-i386: Make most CPU models work with "enforce" out of the box Paolo Bonzini
2014-08-26 18:01   ` Eduardo Habkost
2014-08-27 13:36     ` Paolo Bonzini
2014-08-27 14:05       ` Eduardo Habkost
2014-08-27 14:33         ` Paolo Bonzini [this message]
2014-08-27 15:42           ` Eduardo Habkost
2014-08-27 15:58             ` Andreas Färber
2014-08-27 16:08               ` Eduardo Habkost
2014-08-27 16:14                 ` Andreas Färber
2014-08-27 16:18                 ` Paolo Bonzini
2014-08-27 16:34                   ` 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=53FDEC52.5040909@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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).