From: Joerg Roedel <joerg.roedel@amd.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org, joro@8bytes.org, anthony@codemonkey.ws,
avi@qumranet.com
Subject: Re: [PATCH 0/9] Add support for nested SVM (kernel) v3
Date: Fri, 19 Sep 2008 16:36:00 +0200 [thread overview]
Message-ID: <20080919143600.GO24392@amd.com> (raw)
In-Reply-To: <1221658886-14109-1-git-send-email-agraf@suse.de>
On Wed, Sep 17, 2008 at 03:41:17PM +0200, Alexander Graf wrote:
> To be usable, this patchset requires the two simple changes in the userspace
> part, that I sent to the list with the first version.
>
> Thanks for reviewing!
Ok, with the patch attached applied on-top of your patches I got a
recent KVM running inside KVM. And it doesn't feel very slow :-)
I will do some benchmarks in the next days to get real numbers. The
patches look good so far.
But I think for now we should disable the feature by default and allow
enabling it from userspace until we are sure we don't introduce any
security hole and don't destroy migration with it. We can add a
-nested-virt parameter to qemu to enable it for the guest then.
Another thing missing is the SVM feature CPUID function. It is used to
find out the number of ASIDs available. But this is a minor issue as
long as we only run KVM inside KVM.
Joerg
--
| AMD Saxony Limited Liability Company & Co. KG
Operating | Wilschdorfer Landstr. 101, 01109 Dresden, Germany
System | Register Court Dresden: HRA 4896
Research | General Partner authorized to represent:
Center | AMD Saxony LLC (Wilmington, Delaware, US)
| General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy
next prev parent reply other threads:[~2008-09-19 14:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 13:41 [PATCH 0/9] Add support for nested SVM (kernel) v3 Alexander Graf
2008-09-17 13:41 ` [PATCH 1/9] Add CPUID feature flag for SVM v3 Alexander Graf
2008-09-17 13:41 ` [PATCH 2/9] Clean up VINTR setting v3 Alexander Graf
2008-09-17 13:41 ` [PATCH 3/9] Add helper functions for nested SVM v3 Alexander Graf
2008-09-17 13:41 ` [PATCH 4/9] Implement GIF, clgi and stgi v3 Alexander Graf
2008-09-17 13:41 ` [PATCH 5/9] Implement hsave v3 Alexander Graf
2008-09-17 13:41 ` [PATCH 6/9] Add VMLOAD and VMSAVE handlers v3 Alexander Graf
2008-09-17 13:41 ` [PATCH 7/9] Add VMRUN handler v3 Alexander Graf
2008-09-17 13:41 ` [PATCH 8/9] Add VMEXIT handler and intercepts v3 Alexander Graf
2008-09-17 13:41 ` [PATCH 9/9] Allow setting the SVME bit v3 Alexander Graf
2008-09-19 15:59 ` [PATCH 7/9] Add VMRUN handler v3 Joerg Roedel
2008-09-25 17:32 ` Alexander Graf
2008-09-25 17:37 ` Joerg Roedel
2008-09-25 20:00 ` Alexander Graf
2008-09-25 21:22 ` joro
2008-09-27 12:59 ` Avi Kivity
2008-09-27 12:58 ` Avi Kivity
2008-09-25 18:47 ` [PATCH 4/9] Implement GIF, clgi and stgi v3 Joerg Roedel
2008-09-25 19:55 ` Alexander Graf
2008-09-25 21:27 ` Joerg Roedel
2008-09-26 9:01 ` Alexander Graf
2008-09-27 12:55 ` Avi Kivity
2008-09-27 12:52 ` Avi Kivity
2008-09-19 14:36 ` Joerg Roedel [this message]
2008-09-19 14:39 ` [PATCH 0/9] Add support for nested SVM (kernel) v3 Joerg Roedel
2008-09-19 15:56 ` Joerg Roedel
2008-10-15 17:07 ` Alexander Graf
2008-09-19 21:48 ` First performance numbers Joerg Roedel
2008-09-20 1:30 ` Avi Kivity
2008-09-20 6:55 ` Joerg Roedel
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=20080919143600.GO24392@amd.com \
--to=joerg.roedel@amd.com \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.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).