All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jin Guojie" <jinguojie@loongson.cn>
To: "Richard Henderson" <rth@twiddle.net>
Cc: "Aurelien Jarno" <aurelien@aurel32.net>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] tcg/mips: Add support for mips64el backend
Date: Wed, 16 Nov 2016 09:58:41 +0800	[thread overview]
Message-ID: <tencent_48EFCCEA3EEC41D372319D48@qq.com> (raw)

Richard,

I am ready to participate in testing your v2 patch on Loongson.
The work of updating the patch against master can also be done by us if you don't have time.
I think the tcg/MIPS code between Feb 2016 and now has not significant difference.

However, Loongson only implements little-endian mips32/mips64 ISA,
so the problem Aurelien discovered for mips32 big-endian hosts can not be tested on Loongson.

Loongson has a donation plan for relevant open-source project.
The MIPS related modules in QEMU will be our focus of support.
We can donate two Loongson machines for QEMU maintainers and developers.
You can send me your delivery address in private email.
We welcome your recommendation of other developers you think who are in need of Loongson machines.

Jin Guojie

 
------------------ Original ------------------
From:  "Richard Henderson";<rth@twiddle.net>;
Send time: Wednesday, Nov 16, 2016 5:37 AM
To: "Jin Guojie"<jinguojie@loongson.cn>; "qemu-devel"<qemu-devel@nongnu.org>; 
Cc: "Aurelien Jarno"<aurelien@aurel32.net>; 
Subject:  Re: [Qemu-devel] [PATCH] tcg/mips: Add support for mips64el backend



On 11/14/2016 10:33 AM, Jin Guojie wrote:
> I want listen to your advice. Should I test your v2 patch on Loongson
> and use it? Or whether it is worth modifying my patch and resubmit it
> according to your review comments?

I would like very much if you would test my patch on Loongson (or a 
re-submission of my patch; I could perhaps prepare that against master in the 
next few days).

If it is possible, I would like if you could help fix the problems that 
Aurelien discovered with my patch.  I have no access to mips hardware myself, 
so all of the development that I was doing was from within a qemu itself.  As 
you can imagine, qemu-in-qemu is very very slow.

At the time I was hoping that people from imgtec would be able to help, but 
that never came to pass.  Oh well.


r~

             reply	other threads:[~2016-11-16  2:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16  1:58 Jin Guojie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-11  7:20 [Qemu-devel] [PATCH] tcg/mips: Add support for mips64el backend jinguojie
2016-11-13  7:56 ` Richard Henderson
2016-11-14  9:33   ` Jin Guojie
2016-11-14 16:24     ` Aurelien Jarno
2016-11-15 21:37     ` Richard Henderson
2016-11-16 10:52       ` James Hogan

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=tencent_48EFCCEA3EEC41D372319D48@qq.com \
    --to=jinguojie@loongson.cn \
    --cc=aurelien@aurel32.net \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.