On Thu, Jun 05, 2014 at 01:45:06PM -0600, Eric Blake wrote: > 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. Personally, I wouldn't mind about supporting it forever, as its implementation is very simple. But "x-allow-emulation" would be a good way to make GET_EMULATED_CPUID available for developers who want to test it, without any commitment to a specific API. -- Eduardo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
