From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: question on #UD emulation Date: Sun, 16 Dec 2007 17:07:03 +0200 Message-ID: <47653F17.3060409@qumranet.com> References: <10EA09EFD8728347A513008B6B0DA77A02858E27@pdsmsx411.ccr.corp.intel.com> <47650CD8.5060401@qumranet.com> <10EA09EFD8728347A513008B6B0DA77A02858E8E@pdsmsx411.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: "Dong, Eddie" Return-path: In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A02858E8E-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Dong, Eddie wrote: > > >> Since we don't emulate 3Dnow instructions, a #UD will be >> injected instead. >> >> > OK, how many architecture specific instructiosn are emulated now? > Just vmcall/vmmcall (which is emulated once, then patched). > Or what is planed to be implemented? If no, then adding those > emulation in KVM just means dead code. sysenter/sysexit (which aren't implemented in amd compatibility mode) and syscall/sysret (which aren't implemented in intel compatibility mode). Both are only used for 32-bit userspace on 64-bit guests, so they aren't too critical. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace