qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jun Koi" <junkoi2004@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] May I get a document about detailed architecture of QEMU
Date: Fri, 29 Aug 2008 10:47:25 +0900	[thread overview]
Message-ID: <fdaac4d50808281847m7ed2f589h1b87feed122b60ed@mail.gmail.com> (raw)
In-Reply-To: <f284c33d0808281839l240956e9p6c88bb996a54058a@mail.gmail.com>

On Fri, Aug 29, 2008 at 10:39 AM, Mulyadi Santosa
<mulyadi.santosa@gmail.com> wrote:
> 2008/8/28  <linemin2001@yahoo.com.tw>:
>>
>>
>> Hello,
>>
>> I have a lot of interests in QEMU.
>> I want to learn how qemu work in detail.
>> But, the source code are huge, which let me confused where i should start from.
>> So, may i request for a detail document of QEMU detailed architecture for source code.
>
> Try
> http://www.usenix.org/publications/library/proceedings/usenix05/tech/freenix/bellard.html
>
> and don't miss:
> http://libvncserver.sourceforge.net/qemu/qemu-porting.html
>

The problem is those docs are quite out-of-date. Would be very useful
if somebody writes about the new architecture (like TCG, ....) to
update them.

In recent version of Xen, the developers write up (a bit, but still
very useful) to introduce each single new feature of the new release.
Would that be wonderful if we can do the same thing when something
important is merged???

Thanks,
Jun

  parent reply	other threads:[~2008-08-29  1:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  8:47 [Qemu-devel] May I get a document about detailed architecture of QEMU linemin2001
2008-08-29  1:39 ` Mulyadi Santosa
2008-08-29  1:45   ` Paul Brook
2008-08-29  1:47   ` Jun Koi [this message]
2008-08-29  1:52     ` Jun Koi
2008-08-29  3:09       ` Anthony Liguori
2008-08-29  2:01     ` Mulyadi Santosa

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=fdaac4d50808281847m7ed2f589h1b87feed122b60ed@mail.gmail.com \
    --to=junkoi2004@gmail.com \
    --cc=qemu-devel@nongnu.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).