From: Thomas Treutner <thomas@scripty.at>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: Virtualization Performance: Intel vs. AMD
Date: Tue, 17 Nov 2009 11:23:01 +0100 [thread overview]
Message-ID: <200911171123.01923.thomas@scripty.at> (raw)
In-Reply-To: <4B012583.9060706@redhat.com>
On Monday 16 November 2009 11:12:19 Avi Kivity wrote:
> > Anyways, I'm just curious, as this feature is
> > primarily interesting for development, IMHO.
>
> No, it's primarily interesting for performance.
I think I confused NPT with support for nested virtualization (which I think
no one except devs would have a use case for). Thanks for the pointer.
-t
next prev parent reply other threads:[~2009-11-17 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 12:22 Virtualization Performance: Intel vs. AMD Andreas Winkelbauer
2009-11-15 13:05 ` Neil Aggarwal
2009-11-15 15:55 ` Thomas Treutner
2009-11-16 10:12 ` Avi Kivity
2009-11-17 10:23 ` Thomas Treutner [this message]
2009-11-15 15:56 ` Thomas Treutner
2009-11-15 17:33 ` Neil Aggarwal
2009-11-15 17:54 ` Thomas Fjellstrom
2009-11-15 17:59 ` Neil Aggarwal
2009-11-15 22:29 ` Gordan Bobic
2009-11-15 23:03 ` Thomas Fjellstrom
2009-11-15 23:50 ` Gordan Bobic
2009-11-16 12:02 ` Andi Kleen
2009-11-16 12:10 ` Avi Kivity
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=200911171123.01923.thomas@scripty.at \
--to=thomas@scripty.at \
--cc=avi@redhat.com \
--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