From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [RFC PATCH] Emulate MOVBE Date: Wed, 10 Apr 2013 13:21:37 +0300 Message-ID: <20130410102134.GC17919@redhat.com> References: <20130409234602.GI5077@pd.tnic> <20130410112942.07dfc167@slackpad> <20130410100845.GB17919@redhat.com> <20130410101721.GC13394@pd.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andre Przywara , kvm@vger.kernel.org, =?utf-8?B?SsO2cmcgUsO2ZGVs?= , "H. Peter Anvin" , x86-ml , kvm@vger-kernel.org To: Borislav Petkov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:57342 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752725Ab3DJKV4 (ORCPT ); Wed, 10 Apr 2013 06:21:56 -0400 Content-Disposition: inline In-Reply-To: <20130410101721.GC13394@pd.tnic> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Apr 10, 2013 at 12:17:21PM +0200, Borislav Petkov wrote: > On Wed, Apr 10, 2013 at 01:08:46PM +0300, Gleb Natapov wrote: > > We can add the emulation, but we should not start announcing the > > instruction availability to a guest if host cpu does not have it > > by default. This may trick a guest into thinking that movbe is the > > fastest way to do something when it is not. > > That could be a problem because kernels compiled for atom look at CPUID > to check for MOVBE support and refuse to continue if there's none. > You will still be able to force it on qemu command line by adding +movbe to cpu definition, it just not be the default. -- Gleb.