From: Eric Blake <eblake@redhat.com>
To: Borislav Petkov <bp@alien8.de>, Eduardo Habkost <ehabkost@redhat.com>
Cc: "Michael Mueller" <mimu@linux.vnet.ibm.com>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, "Alexander Graf" <agraf@suse.de>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Gabriel L. Somlo" <gsomlo@gmail.com>,
"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [RFC 0/2] GET_EMULATED_CPUID support with "allow-emulation" option
Date: Thu, 05 Jun 2014 13:45:06 -0600 [thread overview]
Message-ID: <5390C8C2.2030508@redhat.com> (raw)
In-Reply-To: <20140605192421.GA26110@pd.tnic>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
On 06/05/2014 01:24 PM, Borislav Petkov wrote:
> On Thu, Jun 05, 2014 at 04:12:08PM -0300, Eduardo Habkost wrote:
>> In the meantime, we could:
>>
>> * Include the less fine-tuned "allow-emulation" (or
>> "allow-experimental-features") option, which is implemented by this
>> series, for people who use "enforce" and/or don't care too much about
>> getting other experimental features enabled.
>> * Wait until somebody implements "feature=force".
>
> What are you going to do with "allow-emulation" after this? It will
> become an API and you'll have to support it.
If you're worried about not needing the option forever, name it
x-allow-emulation; we've already documented that anything with x- prefix
is fair game for subsequent removal.
--
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-06-05 19:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 16:12 [RFC 0/2] GET_EMULATED_CPUID support with "allow-emulation" option Eduardo Habkost
2014-06-05 16:24 ` Alexander Graf
2014-06-05 16:26 ` Paolo Bonzini
2014-06-05 16:40 ` Alexander Graf
2014-06-05 16:44 ` Paolo Bonzini
2014-06-05 16:45 ` Alexander Graf
2014-06-05 16:52 ` Paolo Bonzini
2014-06-05 16:54 ` Alexander Graf
2014-06-05 16:57 ` Paolo Bonzini
2014-06-05 17:19 ` Eduardo Habkost
2014-06-05 17:39 ` Paolo Bonzini
2014-06-05 18:02 ` Eduardo Habkost
2014-06-05 19:12 ` Eduardo Habkost
2014-06-05 19:24 ` [Qemu-devel] " Borislav Petkov
2014-06-05 19:45 ` Eric Blake [this message]
2014-06-05 19:52 ` Eduardo Habkost
2014-06-05 16:58 ` Alexander Graf
2014-06-05 17:48 ` Eduardo Habkost
2014-06-05 22:24 ` Alexander Graf
2014-06-06 1:21 ` Borislav Petkov
2014-06-06 2:37 ` Eduardo Habkost
2014-06-06 11:16 ` Alexander Graf
2014-06-06 18:38 ` Eduardo Habkost
2014-06-05 17:17 ` Eduardo Habkost
2014-06-05 17:38 ` Paolo Bonzini
2014-06-05 17:52 ` Eduardo Habkost
2014-06-05 17:34 ` Eduardo Habkost
2014-06-06 13:29 ` gleb
2014-06-05 18:11 ` [Qemu-devel] " Eduardo Habkost
[not found] ` <1401984741-26882-3-git-send-email-ehabkost@redhat.com>
2014-06-05 19:57 ` [RFC 2/2 v2] target-i386: Add "x-allow-emulation" X86CPU property Eduardo Habkost
2014-06-05 22:27 ` Alexander Graf
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=5390C8C2.2030508@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=bp@alien8.de \
--cc=ehabkost@redhat.com \
--cc=gsomlo@gmail.com \
--cc=imammedo@redhat.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mimu@linux.vnet.ibm.com \
--cc=mst@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