From: Michael Eager <eager@eagerm.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Internal documentation
Date: Wed, 12 Dec 2012 06:57:29 -0800 [thread overview]
Message-ID: <50C89B59.7000707@eagerm.com> (raw)
In-Reply-To: <50C893E5.8010806@suse.de>
On 12/12/2012 06:25 AM, Andreas Färber wrote:
> 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.
Thanks. I've been using openrisc as well as others as examples.
It isn't clear whether the support will be submitted. The target
is a proprietary processor. So I don't get the benefit of public
review of the code.
> 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. :)
Thanks.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
prev parent reply other threads:[~2012-12-12 14:57 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
2012-12-12 14:57 ` Michael Eager [this message]
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=50C89B59.7000707@eagerm.com \
--to=eager@eagerm.com \
--cc=afaerber@suse.de \
--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 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).