From: "Andreas Färber" <afaerber@suse.de>
To: Michael Eager <eager@eagerm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Internal documentation
Date: Wed, 12 Dec 2012 15:25:41 +0100 [thread overview]
Message-ID: <50C893E5.8010806@suse.de> (raw)
In-Reply-To: <50C77E2D.4030901@eagerm.com>
Hi,
Am 11.12.2012 19:40, schrieb Michael Eager:
> Is there any internal documentation for QEMU?
>
> I'm adding support for a new processor. I'm currently
> adding semihosting support and a new command line option.
> I find that I'm reading a lot of uncommented code and
> trying to reverse engineer QEMU's design by reading how
> various targets are implemented.
>
> Is there a better way?
Look at the latest added target-openrisc in qemu.git and/or at my
target-rl78 at GitHub.com/afaerber/qemu-rl78/. That will also give you
some ideas how to split your new target into reviewable patches.
Also look at the mailing list, you may find old/bad examples in our code
base but patch review usually points out the right ways to do things
nowadays. When in doubt, ask. :)
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-12-12 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 18:40 [Qemu-devel] Internal documentation Michael Eager
2012-12-12 13:39 ` Stefan Hajnoczi
2012-12-12 14:34 ` Michael Eager
2012-12-12 15:00 ` Peter Maydell
2012-12-12 14:25 ` Andreas Färber [this message]
2012-12-12 14:57 ` Michael Eager
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=50C893E5.8010806@suse.de \
--to=afaerber@suse.de \
--cc=eager@eagerm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.