From: "Emilio G. Cota" <cota@braap.org>
To: qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>,
Aurelien Jarno <aurelien@aurel32.net>,
Yongbok Kim <yongbok.kim@mips.com>
Subject: [Qemu-devel] [PATCH 0/4] target/mips: translator loop conversion
Date: Thu, 15 Feb 2018 21:02:48 -0500 [thread overview]
Message-ID: <1518746572-14747-1-git-send-email-cota@braap.org> (raw)
Tested with Aurelien's debian wheezy image for mips64.
The third patch is just to improve the diff--saves about 20%
of diff lines in patch 4, but feel free to squash it with the latter.
Thanks,
Emilio
next reply other threads:[~2018-02-16 2:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 2:02 Emilio G. Cota [this message]
2018-02-16 2:02 ` [Qemu-devel] [PATCH 1/4] target/mips: convert to DisasJumpType Emilio G. Cota
2018-02-16 2:02 ` [Qemu-devel] [PATCH 2/4] target/mips: convert to DisasContextBase Emilio G. Cota
2018-02-16 2:02 ` [Qemu-devel] [PATCH 3/4] target/mips: use *ctx for DisasContext Emilio G. Cota
2018-02-16 2:02 ` [Qemu-devel] [PATCH 4/4] target/mips: convert to TranslatorOps Emilio G. Cota
2018-02-22 14:08 ` [Qemu-devel] [PATCH 0/4] target/mips: translator loop conversion no-reply
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=1518746572-14747-1-git-send-email-cota@braap.org \
--to=cota@braap.org \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=yongbok.kim@mips.com \
/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).