From: Stefan Hajnoczi <stefanha@gmail.com>
To: Matthew Fortune <Matthew.Fortune@mips.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Aleksandar Rikalo <Aleksandar.Rikalo@mips.com>,
Paul Burton <Paul.Burton@mips.com>,
Stefan Markovic <Stefan.Markovic@mips.com>,
Dimitrije Nikolic <Dimitrije.Nikolic@mips.com>,
James Hogan <James.Hogan@mips.com>,
Yongbok Kim <Yongbok.Kim@mips.com>
Subject: Re: [Qemu-devel] Introducing a nanoMIPS port for QEMU
Date: Tue, 1 May 2018 17:21:04 +0100 [thread overview]
Message-ID: <CAJSP0QVxfQKQeAJ0LjrXb61OidiKDacih_HDSw_ucMvLDrdtyw@mail.gmail.com> (raw)
In-Reply-To: <02284e13e9c541cda32051204e64fa66@mips.com>
On Tue, May 1, 2018 at 4:07 PM, Matthew Fortune
<Matthew.Fortune@mips.com> wrote:
> QEMU specific details
> ====================
>
> The nanoMIPS QEMU port borrows a significant amount of logic from the MIPS
> port. Most instructions in nanoMIPS exist in one of the other MIPS ISAs, which
> allows the new decoder to hook into existing logic. Some of the more
> interesting technical changes include:
>
> - The Unified Hosting Interface (UHI) for semihosting is supported and,
> in-keeping with the aims of the interface, the same ABI is used with nanoMIPS
> as MIPS
> - Linux user-mode support has been updated significantly, compared to MIPS, to
> follow the new nanoMIPS ABI which utilizes most of the generic syscall and
> signal infrastructure from the Linux kernel
>
> The QEMU build targets for nanoMIPS are nanomips-softmmu and
> nanomips-linux-user, rather than the existing mips targets, because nanoMIPS is
> not designed for use alongside any other MIPS ISA.
>
> QEMU contributors:
>
> - QEMU
> Yongbok Kim, Stefan Markovic, Aleksandar Rikalo, Dimitrije Nikolic
> Aleksandra Karadzic, Matthew Fortune, Paul Burton, James Hogan
Congratulations! The upstreaming effort of a significant out-of-tree
project like this often takes longer than expected, but several of you
are already QEMU sub-maintainers so that will make it easier.
Please consider submitting a KVM Forum (October 24-26 in Edinburgh,
UK) presentation that highlights aspects of the architecture and how
to emulate it in QEMU:
https://events.linuxfoundation.org/events/kvm-forum-2018/
Stefan
prev parent reply other threads:[~2018-05-01 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 15:07 [Qemu-devel] Introducing a nanoMIPS port for QEMU Matthew Fortune
2018-05-01 16:21 ` Stefan Hajnoczi [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=CAJSP0QVxfQKQeAJ0LjrXb61OidiKDacih_HDSw_ucMvLDrdtyw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=Aleksandar.Rikalo@mips.com \
--cc=Dimitrije.Nikolic@mips.com \
--cc=James.Hogan@mips.com \
--cc=Matthew.Fortune@mips.com \
--cc=Paul.Burton@mips.com \
--cc=Stefan.Markovic@mips.com \
--cc=Yongbok.Kim@mips.com \
--cc=qemu-devel@nongnu.org \
/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).