From: Blue Swirl <blauwirbel@gmail.com>
To: Renjith Ravindran <renjithforever@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] documentation on qemu
Date: Wed, 27 Apr 2011 21:54:07 +0300 [thread overview]
Message-ID: <BANLkTimfwqyun3CgL8TNdJPrhc2G+Qb2sA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimcUMFzz_+9SS-vU5m5B9Es9JgGgA@mail.gmail.com>
On Wed, Apr 27, 2011 at 8:20 PM, Renjith Ravindran
<renjithforever@gmail.com> wrote:
> hi all..
> i am renjith a cs student from inda. I am 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 high
> 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 thought it
> could be useful to other beginners. It would be good if someone here could
> review it. I am attaching the chapter from my report. pls tell if the 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...
next prev parent reply other threads:[~2011-04-27 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 17:20 [Qemu-devel] documentation on qemu Renjith Ravindran
2011-04-27 18:54 ` Blue Swirl [this message]
2011-04-28 6:51 ` 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=BANLkTimfwqyun3CgL8TNdJPrhc2G+Qb2sA@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=renjithforever@gmail.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).