qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH][RFC] SVM support
Date: Thu, 23 Aug 2007 12:14:38 +0300	[thread overview]
Message-ID: <46CD4FFE.1090809@qumranet.com> (raw)
In-Reply-To: <46CC9BF7.6040002@suse.de>

Alexander Graf wrote:
> Blue Swirl wrote:
>   
>> On 8/22/07, Alexander Graf <agraf@suse.de> wrote:
>>   
>>     
>>> - All interceptions (well, maybe I did oversee one or two)
>>>     
>>>       
>> Nice work! For better performance, you should do the op.c checks
>> statically at translation time (if possible).
>>
>>
>>   
>>     
> Thanks. I thought about that first as well, but can't. The information
> if an intercept should occur is defined in the VMCB, which is passed as
> argument on VMRUN (so whenever one enters the VM). This means that the
> very same TB can be executed with completely different intercepts, which
> means I have to fall back to runtime detection in op.c.
>   

You can have the intercept vector be a part of the TB lookup key.  So, 
if the same code is executed natively, or with different intercept 
vectors, it gets a different TB.  Qemu already does this for a number of 
things like cpu operating mode,  cs base, etc.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2007-08-23  9:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 19:58 [Qemu-devel] [PATCH][RFC] SVM support Alexander Graf
2007-08-22 20:19 ` Blue Swirl
2007-08-22 20:26   ` Alexander Graf
2007-08-23  9:14     ` Avi Kivity [this message]
2007-08-23  9:05 ` Avi Kivity
2007-08-24 17:13 ` Alexander Graf
2007-08-24 23:55   ` Fabrice Bellard
2007-08-25  9:57     ` Alexey Eremenko
2007-08-25 12:30       ` Alexander Graf
2007-08-25 17:51         ` Mulyadi Santosa

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=46CD4FFE.1090809@qumranet.com \
    --to=avi@qumranet.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).