qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: WANG Xuerui <i.qemu@xen0n.name>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Song Gao" <gaosong@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 Developers" <qemu-devel@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Add LoongArch support to RISU?
Date: Sun, 26 Sep 2021 23:14:55 +0800	[thread overview]
Message-ID: <48a408cf-91e9-76ce-a2e3-8000f5177d2c@xen0n.name> (raw)
In-Reply-To: <e5d5a725-d2f3-8866-4882-11632adb6f52@amsat.org>

(also adding qemu-devel to Cc)

On 9/26/21 16:25, 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].
I skimmed over the source code in the afternoon, and indeed the 
encodings are textbook example of what should be auto-generated. However 
I didn't find the DSL syntax to be particularly palatable... maybe I was 
just reading a bit too quickly though.
> Do you know developers / companies who might be interested in working
> on this?

As Song replied, Loongson Corporation should be very interested in 
testing their own offerings. This collaboration is exactly what we as a 
community strive for, and I'll happily review any code here or in 
loongarch-opcodes repo for that.

>
> 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


      parent reply	other threads:[~2021-09-26 15:18 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   ` Add LoongArch support to RISU? Philippe Mathieu-Daudé
2021-09-27  8:14     ` Stefan Hajnoczi
2021-09-26 15:14 ` WANG Xuerui [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=48a408cf-91e9-76ce-a2e3-8000f5177d2c@xen0n.name \
    --to=i.qemu@xen0n.name \
    --cc=alex.bennee@linaro.org \
    --cc=chenhuacai@kernel.org \
    --cc=f4bug@amsat.org \
    --cc=gaosong@loongson.cn \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --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).