qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Hanson\, Seth" <shanson@sandia.gov>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: Adding New, Unsupported ISA to Qemu
Date: Tue, 05 Nov 2019 09:51:07 +0000	[thread overview]
Message-ID: <87d0e6k5x0.fsf@linaro.org> (raw)
In-Reply-To: <1572911399018.17766@sandia.gov>


Hanson, Seth via <qemu-devel@nongnu.org> writes:

> Hello,
>
>
> I'm looking for in-depth documentation pertaining to how an unsupported 16 bit RISC ISA can be emulated in Qemu.
>
>
> I've referenced this:
>
>
> https://wiki.qemu.org/Documentation/TCG

I've updated the wiki page to include links to all the TCG documentation
that exists in the source tree. The will hopefully give you a bit more
of an overview of how things go together.

> and have been hoping there's additional, related documentation that I've overlooked.
>
>
> Please advise.

Generally for new targets the guidance is to do what the newer and more
actively maintained front-ends do. In short a new front-end should:

  * use the common translator_loop
  * should probably use decodetree to reduce boilerplate
  * for system emulation emulate a real life device
  * have someone willing to maintain it once merged

Ideally we like to include at least some basic smoke tests for the
platform (tests/tcg/multiarch/system) which will require a publicly
available toolchain which can be wrapped up in our docker build system.

--
Alex Bennée


  reply	other threads:[~2019-11-05  9:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 23:50 Adding New, Unsupported ISA to Qemu Hanson, Seth via
2019-11-05  9:51 ` Alex Bennée [this message]
2019-11-05 16:42 ` Stefan Hajnoczi
2019-11-05 20:55   ` Peter Maydell
2019-11-05 21:23     ` [EXTERNAL] " Hanson, Seth via
2019-11-05 21:39       ` Peter Maydell
2019-11-05 23:45         ` Philippe Mathieu-Daudé
2019-11-05 21:15   ` Palmer Dabbelt

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=87d0e6k5x0.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shanson@sandia.gov \
    /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).