From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KYt5I-0004va-VJ for qemu-devel@nongnu.org; Thu, 28 Aug 2008 21:47:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KYt5H-0004uZ-DC for qemu-devel@nongnu.org; Thu, 28 Aug 2008 21:47:32 -0400 Received: from [199.232.76.173] (port=40010 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KYt5H-0004uT-3c for qemu-devel@nongnu.org; Thu, 28 Aug 2008 21:47:31 -0400 Received: from wf-out-1314.google.com ([209.85.200.170]:3031) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KYt5G-0003ew-Nc for qemu-devel@nongnu.org; Thu, 28 Aug 2008 21:47:31 -0400 Received: by wf-out-1314.google.com with SMTP id 27so577093wfd.4 for ; Thu, 28 Aug 2008 18:47:26 -0700 (PDT) Message-ID: Date: Fri, 29 Aug 2008 10:47:25 +0900 From: "Jun Koi" Subject: Re: [Qemu-devel] May I get a document about detailed architecture of QEMU In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <843931.62128.qm@web73113.mail.tp2.yahoo.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Fri, Aug 29, 2008 at 10:39 AM, Mulyadi Santosa wrote: > 2008/8/28 : >> >> >> 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