qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Song Gao <gaosong@loongson.cn>, WANG Xuerui <git@xen0n.name>,
	maobibo <maobibo@loongson.cn>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"XiaoJuan Yang" <yangxiaojuan@loongson.cn>,
	"Huacai Chen" <chenhuacai@kernel.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Add LoongArch support to RISU?
Date: Sun, 26 Sep 2021 16:35:37 +0200	[thread overview]
Message-ID: <CAAdtpL73NfnguXd6j+EktFieYiWc3=FqftZ2euwTKRmetm7LVg@mail.gmail.com> (raw)
In-Reply-To: <28636647-b87d-1e5f-dc54-a56bf27b1ccf@loongson.cn>

Hi, I meant to include the qemu-devel@ mailing list in Cc but forgot to...
Doing that now.

On Sun, Sep 26, 2021 at 11:25 AM Song Gao <gaosong@loongson.cn> wrote:
>
> Hi, Phil
>
> On 09/26/2021 04:25 PM, Philippe Mathieu-Daudé wrote:
> > Hi Xuerui,
> >
> > Looking at the script [1] used in your series adding LoongArch TCG
> > backend [2], I think all the bits are in place to also generate most
> > of the files required to run RISU [3] and use it to be able to test
> > Song Gao's LoongArch TCG frontend [4].
> >
> > Do you know developers / companies who might be interested in working
> > on this?
> >
> We can do it. Our plan is to complete LoongArch linux-user emulation, system emulation , TCG backend and others support.
> We plan to submit the system emulation code in mid and late October.  Xue rui had finished TCG backend. So we may doing this work after system emulation.
>
> We welcome others to do the work!

This might be a good project to present to Outreachy internship:
https://lists.gnu.org/archive/html/qemu-devel/2021-08/msg03970.html

 "QEMU will apply for the Outreachy December-March round. This
  internship program offers paid, full-time, remote work internships for
  contributing to open source. QEMU can act as an umbrella organization
  for KVM kernel projects."

Stefan, are we past the deadline for submission?

Regards,

Phil.

> > [1] genqemutcgdefs from
> > https://github.com/loongson-community/loongarch-opcodes
> > [2] https://lists.gnu.org/archive/html/qemu-devel/2021-09/msg06601.html
> > [3] https://git.linaro.org/people/pmaydell/risu.git/tree/README
> > [4] https://lists.gnu.org/archive/html/qemu-devel/2021-09/msg04558.html
> >
>


       reply	other threads:[~2021-09-26 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e5d5a725-d2f3-8866-4882-11632adb6f52@amsat.org>
     [not found] ` <28636647-b87d-1e5f-dc54-a56bf27b1ccf@loongson.cn>
2021-09-26 14:35   ` Philippe Mathieu-Daudé [this message]
2021-09-27  8:14     ` Add LoongArch support to RISU? Stefan Hajnoczi
2021-09-26 15:14 ` WANG Xuerui

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='CAAdtpL73NfnguXd6j+EktFieYiWc3=FqftZ2euwTKRmetm7LVg@mail.gmail.com' \
    --to=f4bug@amsat.org \
    --cc=alex.bennee@linaro.org \
    --cc=chenhuacai@kernel.org \
    --cc=gaosong@loongson.cn \
    --cc=git@xen0n.name \
    --cc=maobibo@loongson.cn \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@redhat.com \
    --cc=yangxiaojuan@loongson.cn \
    /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).