From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: KVM exit on UD interception Date: Tue, 06 May 2014 18:56:38 +0200 Message-ID: <53691446.7070706@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE To: =?UTF-8?B?QWxleGFuZHJ1IER1xaN1?= , kvm@vger.kernel.org Return-path: Received: from mail-ee0-f43.google.com ([74.125.83.43]:33360 "EHLO mail-ee0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750829AbaEFQ4o (ORCPT ); Tue, 6 May 2014 12:56:44 -0400 Received: by mail-ee0-f43.google.com with SMTP id d17so1966038eek.2 for ; Tue, 06 May 2014 09:56:42 -0700 (PDT) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: Il 05/05/2014 17:56, Alexandru Du=C5=A3u ha scritto: > > It seems that re-entering virtualized execution on UD interception > gives the user the flexibility of running binaries with newer > instructions on older hardware, if kvm is able to emulate the newer > instructions. I do not fully understand the details of this scenario, > is there such a scenario or is it likely that ud_interception() will > change? Yes, you are correct. This emulation capability is used in some cases,= =20 including: MOVBE, SYSCALL/SYSENTER on 32-bit guests, VMCALL and VMMCALL= =2E Paolo