From: Gregory Haskins <gregory.haskins@gmail.com>
To: Bruce MaJia <bruce.majia@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: question on KVM run flow on Intel-VT
Date: Wed, 22 Apr 2009 10:05:23 -0400 [thread overview]
Message-ID: <49EF2423.2070306@gmail.com> (raw)
In-Reply-To: <20090422132411.GA10001@LL.wrs.com>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hi Bruce,
Bruce MaJia wrote:
> On Wed, Apr 22, 2009 at 08:55:49PM +0800, MaJia wrote:
>
>> Hi,
>>
>> I am learning kvm + Intel-VT nowadays. Since I am rookie on both kvm and
>> Intel-VT, I got following questions about run flow of kvm on vmx.
>>
The Intel Software Developers Manual, Volume 3B, Chapter 21 is your
friend :)
http://download.intel.com/design/processor/manuals/253669.pdf
HTH,
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]
next prev parent reply other threads:[~2009-04-22 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 12:55 question on KVM run flow on Intel-VT MaJia
2009-04-22 13:24 ` Bruce MaJia
2009-04-22 14:05 ` Gregory Haskins [this message]
2009-04-22 14:55 ` Bruce MaJia
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=49EF2423.2070306@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=bruce.majia@gmail.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