From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jason Thomas <jethomas100@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: VMM Architecture documentation
Date: Wed, 16 Nov 2011 12:00:34 -0500 [thread overview]
Message-ID: <20111116170034.GC2793@phenom.dumpdata.com> (raw)
In-Reply-To: <CABKwQ+pT7LFqmnfGoK5YVsmzqomYjnA6t0jr=RyTVoTjFUDNLw@mail.gmail.com>
On Tue, Nov 15, 2011 at 10:12:14AM -0800, Jason Thomas wrote:
> I am looking for a low level description of the VMM architecture, if one
> exists. Specifically which modules are required for 32 bit guests and which
> are needed for 64 bit guests. Does this exist or do I have to sift through
> the source code to find the differences?
We are kind of working through to make that easier to read.
But I am not actually sure what you mean by 'modules'?
next prev parent reply other threads:[~2011-11-16 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 18:12 VMM Architecture documentation Jason Thomas
2011-11-16 17:00 ` Konrad Rzeszutek Wilk [this message]
2011-11-16 18:50 ` Jason Thomas
2011-11-17 16:04 ` Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2011-11-15 18:58 Jason Thomas
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=20111116170034.GC2793@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jethomas100@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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).