From: "Andreas Färber" <andreas.faerber@web.de>
To: khansa@kics.edu.pk
Cc: peter.maydell@linaro.org, riku.voipio@iki.fi,
qemu-devel@nongnu.org, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH 0/3] MIPS64 user mode emulation in QEMU
Date: Thu, 08 Dec 2011 14:22:28 +0100 [thread overview]
Message-ID: <4EE0BA14.7070601@web.de> (raw)
In-Reply-To: <1323321912-15922-1-git-send-email-khansa@kics.edu.pk>
Am 08.12.2011 06:25, schrieb khansa@kics.edu.pk:
> From: Khansa Butt <khansa@kics.edu.pk>
>
> This is the team work of Ehsan-ul-Haq, Abdul Qadeer, Abdul Waheed, Khansa Butt
> from HPCN Lab KICS UET Lahore.
> In previous patch set we were including Cavium specific instructions along with
> Cavium specifc registers in UME. Because of these register fields we had to bump
> the cpu version up but I noticed that cpu_save() and cpu_load() are not called in
> UME so we decided to postpone Octeon specific changes ( registers and instructions)
> and will include them in our SME work( we are currently working on system mode
> emulation of Octeon board) so we closing the following thread
> http://lists.gnu.org/archive/html/qemu-devel/2011-10/msg02665.html
> Please review this new patch set which is without cavium instruction support.
I really hate to repeat myself... We receive lots of patches per day, so
please make your patches easy to read, easy to understand and easy to
review. If you check qemu-devel or the archives, you'll find many good
examples that get committed - most people get this right on second try.
Please don't ignore our comments from previous series:
You previously sent a v3 series, now there's two unversioned series
again. These should be v4 and v5 and should ALWAYS include a bulleted
change log since initial version. This is to tell apart which is the
latest series and which is superseded. v4 should include something like:
"Changes since v3" (or short "v3 -> v4"):
* Drop CPU load/save from series
v2 -> v3:
...
v1 -> v2:
...
If v5 changed nothing but the cover letter, there would be no need to
resend it, explanations for us can be added as a normal email reply.
If you're missing feedback, best just reply to your cover letter with
"Ping?" so that we have a chance of reviewing the email thread with
previous comments.
More in the individual patches.
Andreas
>
> configure | 1 +
> default-configs/mips64-linux-user.mak | 1 +
> linux-user/main.c | 21 ++-
> linux-user/mips64/syscall.h | 2 +
> linux-user/signal.c | 429 ++++++++++++++++++++++++++++++++-
> target-mips/translate.c | 4 +
> 6 files changed, 444 insertions(+), 14 deletions(-)
> create mode 100644 default-configs/mips64-linux-user.mak
>
prev parent reply other threads:[~2011-12-08 13:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 5:25 [Qemu-devel] [PATCH 0/3] MIPS64 user mode emulation in QEMU khansa
2011-12-08 5:25 ` [Qemu-devel] [PATCH 1/3] linux-user:Support for " khansa
2011-12-08 15:15 ` Andreas Färber
2011-12-09 0:18 ` Andreas Färber
2011-12-14 16:04 ` Richard Henderson
2011-12-08 5:25 ` [Qemu-devel] [PATCH 2/3] target-mips:enabling of 64 bit user mode and floating point operations MIPS_HFLAG_UX is included in env->hflags so that the address computation for LD instruction does not treated as 32 bit code see gen_op_addr_add() in translate.c khansa
2011-12-09 0:04 ` Andreas Färber
2011-12-14 17:05 ` Richard Henderson
2011-12-08 5:25 ` [Qemu-devel] [PATCH 3/3] linux-user:Signal handling for MIPS64 khansa
2011-12-14 16:20 ` Richard Henderson
2011-12-28 11:09 ` Khansa Butt
2011-12-29 10:58 ` Khansa Butt
2011-12-29 11:23 ` Andreas Färber
2011-12-08 13:22 ` Andreas Färber [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=4EE0BA14.7070601@web.de \
--to=andreas.faerber@web.de \
--cc=aurelien@aurel32.net \
--cc=khansa@kics.edu.pk \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).