public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: question on #UD emulation
Date: Sun, 16 Dec 2007 17:07:03 +0200	[thread overview]
Message-ID: <47653F17.3060409@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A02858E8E-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.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

      parent reply	other threads:[~2007-12-16 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16 10:01 question on #UD emulation Dong, Eddie
     [not found] ` <10EA09EFD8728347A513008B6B0DA77A02858E27-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-16 11:32   ` Avi Kivity
     [not found]     ` <47650CD8.5060401-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-16 12:33       ` Joerg Roedel
     [not found]         ` <20071216123318.GB31298-5C7GfCeVMHo@public.gmane.org>
2007-12-16 12:49           ` Dor Laor
     [not found]             ` <47651EDB.2010601-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-16 14:42               ` Dong, Eddie
     [not found]                 ` <10EA09EFD8728347A513008B6B0DA77A02858E8C-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-16 15:04                   ` Avi Kivity
2007-12-16 14:44       ` Dong, Eddie
     [not found]         ` <10EA09EFD8728347A513008B6B0DA77A02858E8E-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-16 15:07           ` Avi Kivity [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47653F17.3060409@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox