From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] KVM: x86: Add instruction length to VCPU event state Date: Sun, 14 Feb 2010 17:10:05 +0200 Message-ID: <4B78124D.3060206@redhat.com> References: <4B76762C.10107@web.de> <20100213152635.GA2511@redhat.com> <4B76E638.5010100@web.de> <20100213182253.GB2511@redhat.com> <4B76F25F.1060009@web.de> <20100213190615.GC2511@redhat.com> <4B76FB89.50107@web.de> <4B77FE47.8010501@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , Gleb Natapov , Marcelo Tosatti , kvm To: Paolo Bonzini Return-path: Received: from mx1.redhat.com ([209.132.183.28]:3812 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750945Ab0BNPKH (ORCPT ); Sun, 14 Feb 2010 10:10:07 -0500 In-Reply-To: <4B77FE47.8010501@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 02/14/2010 03:44 PM, Paolo Bonzini wrote: > On 02/13/2010 08:20 PM, Jan Kiszka wrote: >> But I still fail to see the case where event_exit_inst_len is set to >> anything but 1 or 2 and where it is related to anything else than exits >> at INT3, INT X, or INTO. > > What about BOUND? (I want to hide for suggesting anyone uses that > instruction). If compilers used it, software would run slower, but buffer overflows would be much rarer. -- error compiling committee.c: too many arguments to function