From: Paolo Bonzini <pbonzini@redhat.com>
To: "Eduardo Habkost" <ehabkost@redhat.com>,
qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Cc: Aurelien Jarno <aurelien@aurel32.net>, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v2 0/6] target-i386: Make most CPU models work with "enforce" out of the box
Date: Tue, 26 Aug 2014 14:56:21 +0200 [thread overview]
Message-ID: <53FC83F5.2090905@redhat.com> (raw)
In-Reply-To: <1408999550-20321-1-git-send-email-ehabkost@redhat.com>
Il 25/08/2014 22:45, Eduardo Habkost ha scritto:
>
> TCG users expect the default CPU model to contain most TCG-supported features
> (and it makes sense). See, for example, commit
> f1e00a9cf326acc1f2386a72525af8859852e1df.
It doesn't though (SMAP is the most egregious omission, and probably the
main reason why people use QEMU TCG these days), and it raises the
question of backwards-compatibility of qemu64---should we disable TCG
features in old machine types? Probably yes, but we've never done that.
Paolo
next prev parent reply other threads:[~2014-08-26 12:56 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 ` Paolo Bonzini [this message]
2014-08-26 18:01 ` [Qemu-devel] [PATCH v2 0/6] target-i386: Make most CPU models work with "enforce" out of the box Eduardo Habkost
2014-08-27 13:36 ` Paolo Bonzini
2014-08-27 14:05 ` Eduardo Habkost
2014-08-27 14:33 ` Paolo Bonzini
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=53FC83F5.2090905@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).