qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH][RFC] SVM support
Date: Sat, 25 Aug 2007 01:55:23 +0200	[thread overview]
Message-ID: <46CF6FEB.1080504@bellard.org> (raw)
In-Reply-To: <46CF11B2.5070201@suse.de>


> This is a reworked version of the same patch, where I can now boot into
> a x86_64 Linux kernel.
> I rewrote all the access functions for the VMCB, so this time everything
> should work just fine on BE-machines. As suggested I moved the injection
> detection to translate.c, so the non-virtualized machine should be as
> fast as before (w/o svm support), while the virtual one got a speed
> boost from that as well.
> I removed the EIP hack and set EIP every time an interception occurs, so
> unlike the previous version this patch really should have no negative
> effect on speed any more.
> 
> If any of the people on this list using SVM (kvm developers, maybe xen
> developers) could have a deep look into this I'd be really thankful.

Some notes:

- Saving and restoring CC_SRC and CC_DST is not correct as they do not 
belong to the real processor state. You must save and restore eflags 
correctly instead.

- Avoid using macros when inline functions suffice.

Regards,

Fabrice.

  reply	other threads:[~2007-08-25  1:08 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
2007-08-23  9:05 ` Avi Kivity
2007-08-24 17:13 ` Alexander Graf
2007-08-24 23:55   ` Fabrice Bellard [this message]
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=46CF6FEB.1080504@bellard.org \
    --to=fabrice@bellard.org \
    --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).