From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH RFC 8/9] xen: Generic instruction re-execution mechanism for execute faults Date: Wed, 2 Jul 2014 17:04:12 +0100 Message-ID: <53B42D7C.1000004@citrix.com> References: <1404308041-15461-1-git-send-email-rcojocaru@bitdefender.com> <1404308041-15461-8-git-send-email-rcojocaru@bitdefender.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1404308041-15461-8-git-send-email-rcojocaru@bitdefender.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Razvan Cojocaru , xen-devel@lists.xen.org Cc: Andrei Lutas , tim@xen.org List-Id: xen-devel@lists.xenproject.org On 02/07/14 14:34, Razvan Cojocaru wrote: > The Xen emulator is incapable of handling some instructions, which > leads to the injection of an Invalid Opcode exception (#UD) inside > the guest once an unsupported instruction is encountered. This is (as far as I am aware) simply because Xen's current emulation only expects to emulate instructions which trapped for MMIO or fault reasons. There is no conceptual problem with extending Xen's emulation code, as we are now expecting to have to emulate instructions which would otherwise never have hit x86_emulate. ~Andrew