public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Alessandro Sardo <alessandro.sardo@sintesi80.it>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: KVM architecture docs
Date: Mon, 03 Mar 2008 20:23:27 +0200	[thread overview]
Message-ID: <47CC421F.5070003@qumranet.com> (raw)
In-Reply-To: <47CC1E91.7050207@sintesi80.it>

Alessandro Sardo wrote:
> Hello,
>
> I'm interested in learning the technical details of KVM, possibly up to 
> date with latest versions (KVM changes so fast!). I'm not really geared 
> to development (yet), rather I would like to study its architecture from 
> a security point of view.
>
> I've searched anywhere and all I could find was some basic/marketing 
> stuff, or simple white papers explaining HW virtualization. The wiki 
> currently has some details, but none of them are satisfying enough for 
> my needs :-)
>
> If you're familiar with Xen, I'm looking for the KVM equivalent versions 
> of the following docs:
>
> http://www.cl.cam.ac.uk/research/srg/netos/papers/2003-xensosp.pdf
> http://wiki.xensource.com/xenwiki/XenArchitecture?action=AttachFile&do=get&target=Xen+Architecture_Q1+2008.pdf
>
> Does anything like that exist, or should I go the long way studying QEMU 
> and KVM sources?
>
>   

http://ols.108.redhat.com/2007/Reprints/kivity-Reprint.pdf


Outdated, but as a high level overview should suffice.  The biggest 
change in terms of architecture is that we now use regular Linux 
userspace memory for the guest, which means that normal Linux memory 
management applies to the guest.  This includes swapping, memory 
sharing, large page support, NUMA page placement and migration, etc.



-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-03-03 18:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 15:51 KVM architecture docs Alessandro Sardo
2008-03-03 18:23 ` Avi Kivity [this message]
2008-03-04  4:12   ` Zhao Forrest
2008-03-04  8:25     ` Avi Kivity
2008-03-04  9:02       ` Zhao Forrest
2008-03-04  9:21         ` Avi Kivity
2008-03-04 14:17           ` Javier Guerra
2008-03-04 15:08             ` Avi Kivity
2008-03-05  4:06               ` Zhao Forrest
2008-03-05  5:19                 ` Avi Kivity
2008-03-05  6:05                   ` Zhao Forrest
2008-03-05  6:10                     ` Avi Kivity
2008-03-05  6:38                     ` Avi Kivity
2008-03-05  6:51                   ` Zhao Forrest
2008-03-05  6:58                     ` 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=47CC421F.5070003@qumranet.com \
    --to=avi@qumranet.com \
    --cc=alessandro.sardo@sintesi80.it \
    --cc=kvm-devel@lists.sourceforge.net \
    /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