From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43744) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QF9sb-0007u2-EO for qemu-devel@nongnu.org; Wed, 27 Apr 2011 14:54:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QF9sa-00011j-3T for qemu-devel@nongnu.org; Wed, 27 Apr 2011 14:54:29 -0400 Received: from mail-vw0-f45.google.com ([209.85.212.45]:56772) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QF9sZ-00011c-Tu for qemu-devel@nongnu.org; Wed, 27 Apr 2011 14:54:28 -0400 Received: by vws17 with SMTP id 17so1775330vws.4 for ; Wed, 27 Apr 2011 11:54:27 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Blue Swirl Date: Wed, 27 Apr 2011 21:54:07 +0300 Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] documentation on qemu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Renjith Ravindran Cc: qemu-devel@nongnu.org On Wed, Apr 27, 2011 at 8:20 PM, Renjith Ravindran wrote: > hi all.. > =C2=A0=C2=A0 =C2=A0 =C2=A0 =C2=A0i am renjith a cs student from inda. I a= m new to this list :) > recently i had done some study of qemu as part of an academic project, in > the process i had made some documentation on qemu ..theory and and some h= igh > level code organization etc. > i got info from ppts, qemu forums (discussions of be.stefano and > bluesqirl..if i am right)...and some code reading by myself. I=C2=A0thoug= ht=C2=A0it > could be useful to other=C2=A0beginners. It would be good if someone here= could > review it. =C2=A0I am attaching the chapter from my report. pls tell if t= he doc > is any good. Maybe it can be useful. Perhaps you could also use it to improve QEMU documentation, for example clarifying qemu-tech.texi and adding comments to poorly commented source files? On page 30, the architecture list is slightly misleading. For example, i386 directory contains support for both x86_32 and x86_64, likewise MIPS, SPARC and PPC. p. 31: GCC was used only during QEMU build even with dyngen. A C file containing the ops was compiled with GCC, this was processed by dyngen tool to extract the host machine instructions for each op. p. 36 Figure 7.6: the ops are corrupted. There are a few typos, for example QEMU is not written using correct case in the chapter heading, which repeats on the top of every page...